| 3 | Approval of the Agenda | |
|---|---|---|
| R3-213100 | RAN3#113-e Meeting Agenda | RAN3 Chair |
| 4 | Approval of the minutes from previous meetings | |
| R3-213101 | RAN3#112-e Meeting report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-213194 | Guidelines for RAN3 Electronic Meetings | RAN3 Chairman, RAN3 Vice-Chair |
| 7 | General, protocol principles and issues | |
| R3-213102 | TR 30.531 v1.39.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| 8.1 | New Incoming LSs | |
| R3-213104 | Reply LS on support of PWS over SNPN | CT1 |
| R3-213105 | LS reply on multiple TACs per PLMN | CT1 |
| R3-213106 | Reply LS on introducing extended DRX for RedCap UEs | CT1 |
| R3-213108 | Reply LS to SA2 on Scheduling Location in Advance | RAN1 |
| R3-213109 | LS on Positioning Reference Units (PRUs) for enhancing positioning performance | RAN1 |
| R3-213110 | Reply LS on PDB for new 5QI | RAN1 |
| R3-213111 | LS on Network Switching for MUSIM | RAN2 |
| R3-213112 | LS on establishment/resume cause value and UAC on L2 SL Relay | RAN2 |
| R3-213113 | Reply LS on PDB for new 5QI | RAN2 |
| R3-213115 | LS on lower bound for eDRX cycle length | RAN2 |
| R3-213116 | New LS on UE location aspects in NTN | RAN2 |
| R3-213117 | LS on Paging Subgrouping | RAN2 |
| R3-213118 | Reply LS on Time Synchronization assistance parameters | RAN2 |
| R3-213120 | Reply LS on RACH procedure for HO with PSCell | RAN2 |
| R3-213121 | LS on inter-MN handover without SN change | RAN2 |
| R3-213122 | Reply LS on G-RNTI and G-CS-RNTI for MBS | RAN2 |
| R3-213124 | LS on QoE configuration and reporting related issues | RAN2 |
| R3-213125 | LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility | RAN2 |
| R3-213126 | LS Response to LS on multiple TACs per PLMN | SA2 |
| R3-213127 | Response LS on Scheduling Location in Advance to reduce Latency | SA2 |
| R3-213128 | LS on determination of location estimates in local co-ordinates | SA2 |
| R3-213129 | Reply LS on NAS-based busy indication | SA2 |
| R3-213130 | LS on storage of UE Positioning Capabilities | SA2 |
| R3-213131 | LS on Cell reselection with band-specific network slices | SA2 |
| R3-213133 | Reply LS on UE location aspects in NTN | SA3 |
| R3-213134 | Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions | SA5 |
| R3-213136 | LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | SA6 |
| R3-213137 | Reply LS on support of PWS over NPN | SA |
| R3-213225 | Discussion on inter-MN handover without SN change | ZTE |
| R3-213226 | [DRAFT] Reply LS on inter-MN handover without SN change | ZTE |
| R3-213227 | Clarification on inter-MN handover without SN change in Rel-15 | ZTE |
| R3-213228 | Clarification on inter-MN handover without SN change in Rel-16 | ZTE |
| R3-213249 | Indication for full or delta configuration | Nokia, Nokia Shanghai Bell |
| R3-213250 | Clarification of the RRC config preparation in case of a HO without SN change | Nokia, Nokia Shanghai Bell |
| R3-213251 | Clarification of the RRC config preparation in case of a HO without SN change | Nokia, Nokia Shanghai Bell |
| R3-213252 | Response LS on inter-MN handover without SN change | Nokia, Nokia Shanghai Bell |
| R3-213272 | Proposed response LS to RAN2 on the Inter MN handover without SN change | NEC |
| R3-213323 | [Draft] LS Reply on QoE Configuration and Reporting Related Issues | Ericsson |
| R3-213348 | Discussion on LS about UE location aspects in NTN | Huawei |
| R3-213399 | Signalling and Procedures for supporting Positioning Reference Units | Qualcomm Incorporated |
| R3-213423 | (TP for MDT BL CR for TS37.320) TP on updates related to Measurement Pollution | Ericsson |
| R3-213424 | (draft) LS Reply on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions | Ericsson |
| R3-213425 | LS on Time Synchronization | IEEE 1588 working group |
| R3-213426 | Support of PWS for SNPN | Nokia, Nokia Shanghai Bell |
| R3-213427 | Response LS on Support of PWS for SNPN | Nokia, Nokia Shanghai Bell |
| R3-213428 | Support for Paging Subgroups | Nokia, Nokia Shanghai Bell |
| R3-213429 | Reply LS on Paging Subgroups | Nokia, Nokia Shanghai Bell |
| R3-213430 | Issues related to NAS-based Busy Indication | Nokia, Nokia Shanghai Bell |
| R3-213431 | Response LS on NAS-based Busy Indication | Nokia, Nokia Shanghai Bell |
| R3-213432 | Cell Reselection with band-specific network slices | Nokia, Nokia Shanghai Bell |
| R3-213433 | Response LS on cell reselection with band-specific network slices | Nokia, Nokia Shanghai Bell |
| R3-213522 | Discussion on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Nokia, Nokia Shanghai Bell, BT, BDBOS, BMWi, Home Office, Firstnet, UIC |
| R3-213523 | S1AP Cause value for exceeding the bearer pre-emption rate limitation | Nokia, Nokia Shanghai Bell, BT, BDBOS, BMWi, Home Office, Firstnet, UIC |
| R3-213524 | NGAP Cause value for exceeding the bearer pre-emption rate limitation | Nokia, Nokia Shanghai Bell, BT, BDBOS, BMWi, Home Office, Firstnet, UIC |
| R3-213525 | W1AP Cause value for exceeding the bearer pre-emption rate limitation | Nokia, Nokia Shanghai Bell, BT, BDBOS, BMWi, Home Office, Firstnet, UIC |
| R3-213526 | F1AP Cause value for exceeding the bearer pre-emption rate limitation | Nokia, Nokia Shanghai Bell, BT, BDBOS, BMWi, Home Office, Firstnet, UIC |
| R3-213527 | [Draft] Reply LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Nokia, Nokia Shanghai Bell, |
| R3-213553 | Discussion on the issue raised in the LS R2-2106682 | CATT |
| R3-213554 | [Draft] Reply LS on inter-MN handover without SN change | CATT |
| R3-213568 | Consideration on inter-MN handover without SN change | Huawei |
| R3-213569 | Clarification on delta or full RRC configuration in inter-MN handover without SN change | Huawei |
| R3-213570 | Clarification on delta or full RRC configuration in inter-MN handover without SN change | Huawei |
| R3-213571 | [DRAFT] LS on inter-MN handover without SN change | Huawei |
| R3-213584 | Discussion on SA6 LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Ericsson |
| R3-213585 | [DRAFT] Reply LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Ericsson |
| R3-213606 | Discussion on Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions | Huawei |
| R3-213607 | [DRAFT] Reply to Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions | Huawei |
| R3-213608 | Discussion on Positioning Reference Units (PRUs) for enhancing positioning performance | Huawei |
| R3-213609 | [Draft] reply LS on Positioning Reference Units (PRUs) for enhancing positioning performance | Huawei |
| R3-213610 | Discussion on determination of location estimates in local co-ordinates | Huawei |
| R3-213611 | [Draft] Reply LS on determination of location estimates in local co-ordinates | Huawei |
| R3-213634 | Support of PWS for SNPN | Nokia, Nokia Shanghai Bell |
| R3-213635 | Support of PWS for SNPN | Nokia, Nokia Shanghai Bell |
| R3-213638 | Cell reselection with band-specific network slices | Huawei |
| R3-213639 | [Draft] Reply LS on cell reselection with band-specific network slices | Huawei |
| R3-213640 | Paging Subgrouping | Huawei |
| R3-213641 | [Draft] Reply LS on Paging Subgrouping | Huawei |
| R3-213650 | Busy indication and leaving indication | Qualcomm Incorporated |
| R3-213663 | Consideration on Location aspects in NTN | CATT |
| R3-213664 | [Draft] Reply LS on UE location aspects in NTN | CATT |
| R3-213672 | Consideration on Positioning Reference Units (PRUs) | CATT |
| R3-213678 | [Draft] Reply LS on Positioning Reference Units (PRUs) | CATT |
| R3-213679 | Further discussion on NAS-based busy indication | Huawei |
| R3-213680 | [DRAFT] Reply LS on NAS-based busy indication | Huawei |
| R3-213694 | Further discussion on supporting PWS over SNPN | Qualcomm Incorporated, Ericsson |
| R3-213695 | Removal of ETWS/CMAS restriction in SNPN | Qualcomm Incorporated, Ericsson |
| R3-213697 | Discussion on paging subgrouping for Rel-17 Power saving | Samsung |
| R3-213702 | Discussion on the Inter-MN HO without SN change | Samsung |
| R3-213703 | [Draft] Reply LS on inter-MN handover without SN change | Samsung |
| R3-213726 | Support of PWS for NPN | Huawei |
| R3-213727 | Support of PWS for NPN | Huawei |
| R3-213728 | Support of PWS for NPN | Huawei |
| R3-213729 | [Draft] Reply LS on Support of PWS for NPN | Huawei |
| R3-213765 | Discussion on PWS of SNPN | ZTE Corporation |
| R3-213772 | Discussion on NAS-based busy indication | Ericsson |
| R3-213773 | [DRAFT] Reply LS on NAS-based busy indication | Ericsson |
| R3-213777 | Discussion on Cell reselection information for network slices | Ericsson |
| R3-213778 | LS reply on on Cell reselection with band-specific network slices | Ericsson |
| R3-213783 | Further Considerations on UE Location Aspects in NTN | Ericsson LM |
| R3-213784 | [DRAFT] Reply LS on UE location aspects in NTN (NNSF) | Ericsson LM |
| R3-213785 | [DRAFT] Reply LS on UE location aspects in NTN (Constructed CGI) | Ericsson LM |
| R3-213793 | Response to LS on Cell reselection with band-specific network slice | ZTE |
| R3-213838 | Discussion on the Paging sub-grouping LS from RAN2 | Ericsson |
| R3-213839 | Addition of NR paging subgroups information | Ericsson |
| R3-213840 | Addition of NR paging subgroups information | Ericsson |
| R3-213841 | Draft Reply LS on Paging Subgrouping | Ericsson |
| R3-213843 | Draft Reply LS on Positioning Reference Units | Ericsson |
| R3-213862 | RRC configuration during inter-MN handover without SN change | Ericsson |
| R3-213863 | [DRAFT] Reply LS on inter-MN handover without SN change | Ericsson |
| R3-213864 | Introducing RRC configuration indicator during inter-MN handover without SN change | Ericsson |
| R3-213865 | Introducing RRC configuration indicator during inter-MN handover without SN change | Ericsson |
| R3-213866 | Introducing RRC configuration indicator during inter-MN handover without SN change | Ericsson |
| R3-213867 | Introducing RRC configuration indicator during inter-MN handover without SN change | Ericsson |
| R3-213973 | Discussion on Pre-emption limit issue in MC systems | Samsung |
| R3-213974 | (CR for TS 36.413) Support to address pre-emption limit issue in MC systems | Samsung |
| R3-213975 | (CR for TS 38.413) Support to address pre-emption limit issue in MC systems | Samsung |
| R3-213976 | ReplyLS_Pre-emption limit issue in MC systems | Samsung |
| R3-214026 | Consideration cell reselection with band-specific network slices | LG Electronics |
| R3-214027 | [Draft] Reply LS on cell reselection with band-specific network slices | LG Electronics |
| R3-214051 | [draft] Reply LS on QoE configuration and reporting related issues | ZTE |
| R3-214052 | [DRAFT] Reply LS on UE location aspects in NTN | Huawei |
| R3-214053 | Discussion on Paging Subgrouping | CATT |
| R3-214067 | Discussions on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Huawei |
| R3-214068 | Draft reply LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Huawei |
| R3-214111 | Discussion on QoE configuration and reporting related issues | CMCC |
| R3-214112 | [Draft] Reply LS on QoE configuration and reporting related issues | CMCC |
| R3-214132 | Response to R3-213430, R3-213650, R3-213679, R3-2137728 | ZTE |
| R3-214133 | CB: # 1_InterMNHO_WithoutSNChange - Summary of email discussion | ZTE - moderator |
| R3-214134 | CB: # 2_QoEConfigandReport - Summary of email discussion | CMCC - moderator |
| R3-214135 | CB: # 3_NTNUELocation - Summary of email discussion | CATT - moderator |
| R3-214136 | CB: # 4_MeasPollution - Summary of email discussion | Ericsson - moderator |
| R3-214137 | CB: # 5_PWSoverNPN - Summary of email discussion | Qualcomm - moderator |
| R3-214138 | CB: # 6_UEPowerSaving - Summary of email discussion | Nokia - moderator |
| R3-214139 | CB: # 7_multiUSIM - Summary of email discussion | Huawei - moderator |
| R3-214140 | CB: # 8_BandSpecificNS - Summary of email discussion | ZTE - moderator |
| R3-214141 | CB: # 9_ BearerPreemptionRateLimit - Summary of email discussion | Huawei - moderator |
| R3-214142 | CB: # 10_PositionPRU - Summary of email discussion | Ericsson - moderator |
| R3-214143 | CB: # 11_LocationEst - Summary of email discussion | Huawei - moderator |
| R3-214189 | Response to R3-213522, R3-213973 | Ericsson LM |
| R3-214281 | LS on RAN3 work associated with UE Power Saving | Nokia |
| R3-214294 | Draft Reply LS on Positioning Reference Units | Ericsson |
| R3-214312 | Reply LS on determination of location estimates in local co-ordinates | Huawei |
| R3-214339 | Response to LS on Cell reselection with band-specific network slice | ZTE |
| R3-214345 | [Draft] Reply LS on UE location aspects in NTN | CATT |
| R3-214375 | Response LS on Support of PWS for SNPN | Nokia, Nokia Shanghai Bell |
| R3-214402 | Response LS on PWS Support over SNPN | Nokia, Nokia Shanghai Bell |
| R3-214405 | Removal of ETWS/CMAS restriction in SNPN | Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-214409 | Reply LS on QoE configuration and reporting related issues | CMCC |
| R3-214429 | LS Reply on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions | Ericsson |
| R3-214438 | (TP for BL CR for TS 38.300) Configuration for CGI mapping | CATT, Thales |
| R3-214457 | Reply LS on Positioning Reference Units | Ericsson |
| R3-214471 | Reply LS on QoE configuration and reporting related issues | CMCC |
| R3-214472 | Response to LS on Cell reselection with band-specific network slice | ZTE |
| 8.2 | LSin received during the meeting | |
| R3-214290 | Reply LS on NAS-based busy indication | RAN2 |
| R3-214335 | Reply LS on Report Amount for M4, M5, M6, M7 measurements | RAN2 |
| R3-214356 | Reply LS on Cell reselection with band-specific network slices | RAN2 |
| R3-214420 | Response LS on Multiple TACs per PLMN | RAN2 |
| R3-214425 | Reply LS on the mapping between service types and slice at application | SA2 |
| R3-214426 | LS on Clarification of UE with CAG information in UE subscription | SA2 |
| R3-214431 | LS Reply to SA3 on security protection on RRCResumeRequest message | RAN2 |
| 8.3.1 | RACS Capability Detection with S1/NG HO | |
| R3-213260 | Further discussion on RACS Capability Detection for S1 and NG handover | Qualcomm Incorporated, Vodafone |
| R3-213261 | Detection of RACS support at target during N2/S1 handover | Qualcomm Incorporated, Vodafone |
| R3-213262 | Detection of RACS support at target during N2/S1 handover | Qualcomm Incorporated, Vodafone |
| R3-213263 | [DRAFT] Reply LS on RACS capability detection with S1 and NG handover | Qualcomm Incorporated |
| R3-213364 | Correcting assigned criticality for IEs in transparent handover containers | Ericsson |
| R3-213365 | Correcting assigned criticality for IEs in transparent handover containers | Ericsson |
| R3-213400 | [DRAFT] Reply LS on RACS capability detection with S1 and NG handover | Ericsson |
| R3-213580 | On communication between source and target RAN node at CN handover for non-supported features | Ericsson |
| R3-213581 | Introducing target Criticality Diagnostics in target to source failure container | Ericsson |
| R3-213582 | Introducing target Criticality Diagnostics in target to source failure container | Ericsson |
| R3-213583 | Correcting Presence of the Cell CAG Information IE in ASN.1 | Ericsson |
| R3-213665 | Discussion on RACS capability detection with S1 and NG handover | CATT |
| R3-213666 | [Draft] Reply LS on RACS capability detection with S1 and NG handover | CATT |
| R3-213730 | On RACS capability detection for non-direct-connected nodes | Huawei |
| R3-213731 | On RACS capability detection for non-direct-connected nodes | Huawei |
| R3-213732 | On RACS capability detection for non-direct-connected nodes | Huawei |
| R3-213733 | On IEs with reject criticality in the source and target transparent container | Huawei |
| R3-213734 | On IEs with reject criticality in the source and target transparent container | Huawei |
| R3-213735 | [Draft] Reply LS on RACS capability detection with S1 and NG handover | Huawei |
| R3-214144 | CB: # 12_ RACSCapDetection - Summary of email discussion | Ericsson - moderator |
| R3-214249 | Correcting assigned criticality for IEs in transparent handover containers | Ericsson |
| R3-214250 | Correcting assigned criticality for IEs in transparent handover containers | Ericsson |
| R3-214334 | On IEs with reject criticality in the source and target transparent container | Huawei, Ericsson |
| R3-214373 | Reply LS on RACS capability detection with S1 and NG handover | Ericsson |
| R3-214374 | Correcting assigned criticality for IEs in transparent handover containers | Ericsson, Huawei |
| 8.3.2 | Expected UE Activity Behaviour | |
| R3-213359 | Discussion on PDU Session level "Expected UE activity behaviour" | Ericsson |
| R3-213360 | PDU Session level Expected UE activity behaviour | Ericsson |
| R3-213736 | Finalizing the PDU session level Expected UE Activity Behaviour | Huawei, Lenovo, Motorola Mobility, Qualcomm Incorporated, ZTE |
| R3-213737 | Expected UE Activity Behaviour | Huawei, Lenovo, Motorola Mobility, Qualcomm Incorporated, ZTE |
| R3-213748 | Correction on Expected UE activity behaviour | Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated, ZTE |
| R3-214145 | CB: # 13_ ExpUEActivBehavior - Summary of email discussion | Lenovo - moderato |
| R3-214248 | PDU Session level Expected UE activity behaviour | Ericsson |
| R3-214355 | [DRAFT] Reply LS on PDU Session level "Expected UE activity behaviour" | Ericsson |
| 8.3.3 | E-RABs Cannot Be Handed Over | |
| R3-213413 | Indicating E-RABs that cannot be handed over to 2G/3G or 5G | Ericsson, BT, Vodafone |
| R3-213414 | Indicating E-RABs that cannot be handed over to 2G/3G or 5G | Ericsson, BT, Vodafone |
| R3-213415 | Indicating E-RABs that cannot be handed over to 2G/3G or 5G | Ericsson, BT, Vodafone |
| R3-213434 | Handling E-RABs which cannot be handed over to 3g | Nokia, Nokia Shanghai Bell |
| R3-213749 | On E-RABs that cannot be handed over to 2G/3G | Huawei |
| R3-213750 | On E-RABs that cannot be handed over to 2G/3G | Huawei |
| R3-213794 | E-RABs Cannot Be Handed Over | ZTE |
| R3-213795 | E-RABs Cannot Be Handed Over for S1AP | ZTE |
| R3-213796 | E-RABs Cannot Be Handed Over for X2AP | ZTE |
| R3-214146 | CB: # 14_ERABsCannotHO - Summary of email discussion | ZTE - moderator |
| 9.3.1 | NR-NR DC Configuration Release | |
| R3-213229 | Further discussion on NR-NR DC Configuration Release | ZTE |
| R3-213230 | Clarification for SgNB trigger SCG release in Rel-15 | ZTE |
| R3-213231 | Clarification for SgNB trigger SCG release in Rel-16 | ZTE |
| R3-213232 | [DRAFT] Reply LS on signalling SN initiated release of SCG | ZTE |
| R3-213254 | Consideration on SN-initiated SCG release in EN-DC | Nokia, Nokia Shanghai Bell |
| R3-213273 | Proposed Response LS to RAN2 onSignalling SN initiated release of SCG resource | NEC |
| R3-213476 | SCG Event Indication over F1 | Nokia, Nokia Shanghai Bell |
| R3-213477 | SCG Event Indication over F1 | Nokia, Nokia Shanghai Bell |
| R3-213623 | SCG Event Indication over Xn | Nokia, Nokia Shanghai Bell |
| R3-213624 | SCG Event Indication over Xn | Nokia, Nokia Shanghai Bell |
| R3-213885 | How to release SCG configuration between MN-CU and MN-DU | Ericsson |
| R3-213886 | How to release SCG configuration between MN-CU and MN-DU CR 36.423 | Ericsson |
| R3-213887 | How to release SCG configuration between MN-CU and MN-DU CR 36.423 | Ericsson |
| R3-213979 | Further discussion on SCG release | Huawei, Deutsche Telekom |
| R3-213980 | [DRAFT] LS on signalling SN initiated release of SCG | Huawei |
| R3-213981 | Clarification on SCG release indication | Huawei, Deutsche Telekom |
| R3-213982 | Clarification on SCG release indication | Huawei, Deutsche Telekom |
| R3-213983 | SN triggerred SCG release | Huawei, Deutsche Telekom |
| R3-213984 | SN triggerred SCG release | Huawei, Deutsche Telekom |
| R3-214149 | CB: # 15_SCGConfigRelease - Summary of email discussion | Nokia - moderator |
| 9.3.2.1 | E1 Aspects | |
| R3-213435 | Support of 4g-5g direct data forwarding over E1 with non-shared gNB | Nokia, Nokia Shanghai Bell, China Telecom, CATT |
| R3-213436 | Support of 4g-5g direct data forwarding over E1 with non-shared gNB | Nokia, Nokia Shanghai Bell, China Telecom, CATT |
| R3-213437 | Support of 4g-5g direct data forwarding over E1 with shared gNB | Nokia, Nokia Shanghai Bell |
| R3-213438 | Support of 4g-5g direct data forwarding over E1 with shared gNB | Nokia, Nokia Shanghai Bell |
| R3-213751 | Direct data forwarding for 4G to 5G handover | Huawei, Samsung |
| R3-213792 | Direct data forwarding for 4G to 5G handover | Huawei, Samsung |
| R3-213872 | E1 aspects of inter-system direct data forwarding | Ericsson |
| R3-213873 | Shared SgNB in inter-system direct data forwarding | Ericsson |
| R3-213911 | Data forwarding address allocation for EPC to 5GC handover | Huawei, Samsung, China Telecom |
| R3-213922 | Direct data forwarding for inter-system HO from 4G to 5G | Samsung, LGU+, Huawei |
| R3-213923 | Support of direct data forwarding for inter-system HO from 4G to 5G | Samsung, LGU+, Huawei |
| R3-214150 | CB: # 16_DirectDataFwd_E1aspects - Summary of email discussion | Ericsson - moderator |
| R3-214450 | Data forwarding address allocation for EPC to 5GC handover | Huawei, Samsung, China Telecom, Nokia, Nokia Shanghai Bell, CATT |
| R3-214470 | Support of direct data forwarding for inter-system HO from 4G to 5G | Samsung, LGU+, Huawei, Nokia, Nokia Shanghai Bell |
| 9.3.2.2 | With Mobility Between DC and SA | |
| R3-213369 | SN direct data forwarding | Qualcomm Incorporated |
| R3-213370 | SN direct data forwarding | Qualcomm Incorporated |
| R3-213752 | Direct data forwarding for mobility between DC and SA | Huawei, Samsung |
| R3-213924 | Direct data forwarding for mobility between DC and SA | Samsung, Huawei |
| R3-213925 | Discussion on direct data forwarding for mobility between DC and SA | Samsung, Huawei |
| R3-214151 | CB: # 17_DirectDataFwd_DC - Summary of email discussion | Huawei - moderator |
| 9.3.3 | Lossless Intra-System HO in CP-UP Separation Scenario | |
| R3-213479 | Discussion on Lossless intra-system HO in disaggregated architecture | Nokia, Nokia Shanghai Bell |
| R3-213480 | Lossless intra-system HO in disaggregated architecture | Nokia, Nokia Shanghai Bell |
| R3-213481 | Discussion on Lossless Inter-gNB HO data forwarding | Nokia, Nokia Shanghai Bell |
| R3-213482 | Lossless inter-gNB HO data forwarding | Nokia, Nokia Shanghai Bell |
| R3-213919 | Lossless intra-system HO in dis-aggregated gNB scenario | Samsung, Huawei, Intel Corporation, China Telecom, LGU+, ZTE |
| R3-213920 | Correction of intra-system HO in CP-UP separation scenario | Samsung, Huawei, Intel Corporation, China Telecom, LGU+, ZTE |
| R3-213921 | Correction of intra-system HO in CP-UP separation scenario | Samsung, Huawei, Intel Corporation, China Telecom, LGU+, ZTE |
| R3-214152 | CB: # 18_ Lossless_Intra-systemHO - Summary of email discussion | Samsung - moderator |
| 9.3.4.1 | Other Corrections | |
| R3-213197 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-213198 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-213199 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-213200 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-213201 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-213202 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-213203 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-213204 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom |
| R3-213233 | Correction on EN-DC case | ZTE, Intel Corporation, Lenovo |
| R3-213234 | Clarification on Early status transfer | ZTE, Intel Corporation, Lenovo |
| R3-213264 | Support for handling unknown length of gNB identifier [FLEX_gNB_Len] | Qualcomm Incorporated, Huawei |
| R3-213265 | Support for handling unknown length of gNB identifier [FLEX_gNB_Len] | Qualcomm Incorporated, Huawei |
| R3-213269 | F1AP correction for multi-PLMN deployments | Nokia, Nokia Shanghai Bell, Orange, CATT |
| R3-213270 | Correction for multi-PLMN deployments | Nokia, Nokia Shanghai Bell, Orange, CATT |
| R3-213271 | Correction for multi-PLMN deployments | Nokia, Nokia Shanghai Bell, Orange, CATT |
| R3-213274 | PDU Session level Data Forwarding Information and QoS Flow list | NEC, Samsung, ZTE |
| R3-213275 | Correction of PDU Session level Data Forwarding Information and QoS Flow list | NEC, Samsung, ZTE |
| R3-213276 | Correction of PDU Session level Data Forwarding Information and QoS Flow list | NEC, Samsung, ZTE |
| R3-213277 | Including of NASC IE for EPS to 5GS handover | NEC |
| R3-213278 | Correction of including the NASC IE for EPS to 5GS handover | NEC |
| R3-213279 | Correction of including the NASC IE for EPS to 5GS handover | NEC |
| R3-213298 | Discussion on network based solution for flexible gNB ID length | Huawei, Qualcomm Incorporated |
| R3-213299 | Network based solution for flexible gNB ID length [FLEX_gNB_Len] | Huawei, Qualcomm Incorporated |
| R3-213300 | Network based solution for flexible gNB ID length [FLEX_gNB_Len] | Huawei, Qualcomm Incorporated |
| R3-213314 | CR for TS38.463 on Correction on missing IE of EHC | ZTE |
| R3-213324 | Discussion on removing the restriction of cause value of “procedure cancelled” | CATT |
| R3-213325 | Remove the restriction on cause value “procedure cancelled” for 38.423 (R15) | CATT |
| R3-213355 | Correction on Paging over W1 | Huawei, Orange |
| R3-213356 | Enhancement for EHC contexts | Huawei, China Unicom |
| R3-213357 | Restricting the number of DL EHC contexts – Option 1 | Huawei, China Unicom |
| R3-213358 | Restricting the number of DL EHC contexts – Option 2 | Huawei, China Unicom |
| R3-213371 | Inter MN Resume without SN Change | Qualcomm Incorporated, China Telecom, T-Mobile USA |
| R3-213372 | Inter MN Resume without SN Change (CR to 38.423) | Qualcomm Incorporated, China Telecom, T-Mobile USA |
| R3-213416 | Abnormal conditions in gNB-DU Configuration Update CR 38.473 | Ericsson |
| R3-213417 | Abnormal conditions in gNB-DU Configuration Update CR 38.473 | Ericsson |
| R3-213421 | XnAP Slicing available capacity description alignment | Ericsson, China Unicom, Deutsche Telekom, CMCC, Verizon Wireless |
| R3-213422 | F1AP Slicing available capacity description alignment | Ericsson, China Unicom, Deutsche Telekom, CMCC, Verizon Wireless |
| R3-213439 | Correction of Xn Security | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-213440 | Correction of Xn Security | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-213441 | Correction of MICO mode | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Deutsche Telekom, Huawei |
| R3-213442 | Correction of MICO mode | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Deutsche Telekom, Huawei |
| R3-213443 | Correction of NG Handover | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-213444 | Correction of NG Handover | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-213450 | Correction of data forwarding transport | Nokia, Nokia Shanghai Bell |
| R3-213472 | Discussion on UL Data Split | Nokia, Nokia Shanghai Bell |
| R3-213473 | UL Data Split | Nokia, Nokia Shanghai Bell |
| R3-213484 | Duplicate gNB-DU ID failure | Nokia, Nokia Shanghai Bell |
| R3-213485 | PLMN Not Supported Cause Value | Nokia, Nokia Shanghai Bell |
| R3-213494 | Discussion on E1AP handling for unmapped DL flows | CATT, Intel Corporation, Huawei, China Telecom |
| R3-213495 | CR on E1AP handling for unmapped DL flows | CATT, Intel Corporation, Huawei, China Telecom |
| R3-213496 | CR on E1AP handling for unmapped DL flows | CATT, Intel Corporation, Huawei, China Telecom |
| R3-213512 | CR for 38.460 on E1AP handling for unmapped DL QoS flows | Intel Corporation, CATT, Huawei |
| R3-213513 | X2AP SN Status Transfer description correction for RLC-UM configured with DAPS | Intel Corporation |
| R3-213514 | XnAP SN Status Transfer description correction for RLC-UM configured with DAPS | Intel Corporation |
| R3-213517 | Correction of maximum extended slice support items | NTT DOCOMO INC. |
| R3-213518 | Correction of inter system SON configuration Transfer | NTT DOCOMO INC. |
| R3-213519 | Clarification of DDDS procedure | NTT DOCOMO INC. |
| R3-213520 | Clarification of DDDS procedure | NTT DOCOMO INC. |
| R3-213528 | Discussion on NR-DC UE using IAB | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm, ZTE, Samsung |
| R3-213529 | Support for using IAB for a NR-DC UE | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm, ZTE, Samsung |
| R3-213627 | Deactivation of the MICO mode indication | Huawei, Nokia, Nokia Shanghai-Bell, China Telecom |
| R3-213628 | Deactivation of the MICO mode indication | Huawei, Nokia, Nokia Shanghai-Bell, China Telecom |
| R3-213629 | Correction for UL Data Notification over E1 | Huawei, Intel Corporation, CATT, China Telecom |
| R3-213630 | Correction for UL Data Notification over E1 | Huawei, Intel Corporation, CATT, China Telecom |
| R3-213631 | Correction on AMF auto-recovery | Huawei, Orange, Deutsche Telekom |
| R3-213632 | Correction on AMF auto-recovery | Huawei, Orange, Deutsche Telekom |
| R3-213633 | NAS Non-Delivery | Huawei, CATT, Ericsson, ZTE |
| R3-213636 | Correction of NAS Non Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-213637 | Correction of NAS Non Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-213644 | Correction of served cell information for NPN | Huawei, China Telecom |
| R3-213667 | Further discussion on NAS Non Delivery | CATT, Huawei, ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-213668 | Including Mobility Restriction List in PATH SWITCH REQUEST ACKNOWLEDGE_v16 | CATT |
| R3-213696 | Stage-3 CR on transmission stop for Rel-16 DAPS handover | Samsung, CATT, Intel Corporation |
| R3-213709 | Discussion on F1-U Delay Measurement for QoS Monitoring | Samsung, Verizon Wireless |
| R3-213710 | Correction of F1-U delay measurement for QoS monitoring 1 | Samsung, Verizon Wireless |
| R3-213711 | Correction of F1-U delay measurement for QoS monitoring 2 | Samsung, Verizon Wireless |
| R3-213753 | Ignoring the notification Control for WWC | Huawei, BT |
| R3-213754 | Correcion of QoS monitoring request and disabled | Huawei, ZTE, CMCC |
| R3-213755 | Correcion of QoS monitoring request and disabled | Huawei, ZTE, CMCC |
| R3-213797 | S-NSSAI without SD | ZTE,Lenovo, Motorola Mobility,China Unicom,China Telecom |
| R3-213798 | Correction on SD value for NGAP | ZTE,Lenovo, Motorola Mobility,China Unicom,China Telecom |
| R3-213799 | Correction on SD value for XnAP | ZTE,Lenovo, Motorola Mobility,China Unicom,China Telecom |
| R3-213800 | Correction on SD value for F1AP | ZTE,Lenovo, Motorola Mobility,China Unicom,China Telecom |
| R3-213801 | Correction on SD value for E1AP | ZTE,Lenovo, Motorola Mobility,China Unicom,China Telecom |
| R3-213802 | Misalignment value range for reportInterval IE of MDT for NGAP | ZTE,Lenovo, Motorola Mobility,China Unicom,China Telecom |
| R3-213803 | Misalignment value range for reportInterval IE of MDT for XnAP | ZTE,Lenovo, Motorola Mobility,China Unicom,China Telecom |
| R3-213804 | Missing QoS Flows not Admitted List in NGAP HANDOVER COMMAND | ZTE,Samsung,China Unicom,China Telecom |
| R3-213805 | Correction on NAS non delivery | ZTE, CATT, Huawei |
| R3-213847 | Clarification on the specified maximum length of the Routing ID Octet String | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Inc. |
| R3-213848 | Correction of the NRPPa LMF and RAN UE Measurement IDs extension | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Inc. |
| R3-213849 | Correction of the RAN and LMF UE measurement IDs extension | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Inc. |
| R3-213874 | UL primary path signaling over E1 | Ericsson |
| R3-213880 | UL primary path signaling over E1 | Ericsson |
| R3-213889 | Dynamic ACL | Ericsson |
| R3-213890 | Dynamic ACL over NG CR 38.413 | Ericsson |
| R3-213891 | Dynamic ACL over NG CR 38.413 | Ericsson |
| R3-213899 | Correction on LTE UE RLF report | China Telecom Corporation Ltd. |
| R3-213900 | R16 CR to Correction on LTE UE RLF Report | China Telecom,CATT |
| R3-213901 | CR for TS38.463 on the misalignment of the IE name for the TSC Assistance Information IE in the tabular and the ASN.1 | Samsung |
| R3-213902 | Discussion on security indication in the modification procedure over E1 interface | China Telecom Corporation Ltd. |
| R3-213908 | Rel-15 CR to 38 463 on security indication in the modification procedure over E1 interface | China Telecom Corporation Ltd. |
| R3-213909 | Rel-16 CR to 38 463 on security indication in the modification procedure over E1 interface | China Telecom Corporation Ltd. |
| R3-213912 | Inclusion of RFSP for NG-RAN | Huawei, China Telecom |
| R3-213918 | Correction of RESOURCE STATUS UPDATE | Samsung, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, CATT, Huawei, CMCC |
| R3-213929 | TNL address allocation for direct data forwarding from E-UTRAN to NG-RAN | Samsung, Huawei |
| R3-213930 | Discussion on Security handling for CP-UP separation of IAB-donor | Huawei, Lenovo, Motorola Mobility |
| R3-213931 | Correction on support of Pre-shared key derivation for IAB-donor-CU-UP | Huawei, Lenovo, Motorola Mobility |
| R3-213938 | Correction CR on Network instance for 38.413(R15) | CATT |
| R3-213939 | CR to TS 38463 for Intra gNB-CU-UP DAPS HO | CATT, Intel Corporation |
| R3-213958 | Corrections on positioning | Huawei, CMCC |
| R3-213959 | Adding procedural text for System Frame Number and Slot Number | Huawei, CMCC |
| R3-213960 | Adding procedural text for System Frame Number and Slot Number | Huawei, CMCC |
| R3-213961 | Adding F1AP support of positioning in stage 2 | Huawei, CMCC |
| R3-213962 | Inter MN Resume without SN Change | Huawei, CMCC |
| R3-213963 | Inter MN Resume without SN Change | Huawei, CMCC |
| R3-213993 | Discussion on missing IE of EHC | ZTE |
| R3-213994 | CR for TS38.463 on Correction on missing IE of EHC (option 1) | ZTE |
| R3-213995 | CR for TS38.463 on Correction on missing IE of EHC (option 2) | ZTE |
| R3-213997 | Discussion on E-RAB Modification Indication Procedure | ZTE, China Telecom, China Unicom |
| R3-213998 | Correction for NPN related Served Cell Information (Option 1) [NG_RAN_PRN-Core] | ZTE Corporation |
| R3-213999 | Correction on E-RAB Modification Indication Procedure for Rel-15 | ZTE, China Telecom, China Unicom |
| R3-214000 | Correction on E-RAB Modification Indication Procedure for Rel-16 | ZTE, China Telecom, China Unicom |
| R3-214005 | Correction for NPN related Served Cell Information (Option 2) [NG_RAN_PRN-Core] | ZTE Corporation |
| R3-214017 | Correction of Paging DRX | Huawei, Orange, Deutsche Telekom |
| R3-214018 | Correction of Paging DRX | Huawei, Orange, Deutsche Telekom |
| R3-214019 | Correction of Paging DRX | Huawei, Orange, Deutsche Telekom |
| R3-214020 | Correction of Paging DRX | Huawei, Orange, Deutsche Telekom |
| R3-214021 | Correction of Paging DRX | Huawei, Orange, Deutsche Telekom |
| R3-214022 | Correction of Paging DRX | Huawei, Orange, Deutsche Telekom |
| R3-214023 | Correction on the extension for Index to RAT/Frequency Selection Priority | Huawei, Orange, Deutsche Telekom |
| R3-214024 | Correction for UL PDU Session Information | Huawei, China Telecom |
| R3-214025 | Correction for UL PDU Session Information | Huawei, China Telecom |
| R3-214069 | EN-DC definition in W1 | Huawei, China Unicom |
| R3-214125 | Correction of the IE related to E-UTRA resource coordination in F1AP | Samsung |
| R3-214126 | Correction of the IE related to E-UTRA resource coordination in F1AP | Samsung |
| R3-214153 | CB: # 19_NonNASDelivery - Summary of email discussion | CATT - moderator |
| R3-214154 | CB: # 20_DynamicACL - Summary of email discussion | Ericsson |
| R3-214155 | CB: # 21_UnmappedQoS - Summary of email discussion | CATT - moderator |
| R3-214156 | CB: # 22_EHC - Summary of email discussion | ZTE - moderator |
| R3-214157 | CB: # 23_InterMNResume_withoutSNChange - Summary of email discussion | Qualcomm - moderator |
| R3-214158 | CB: # 24_Flexible_gNBIDlen - Summary of email discussion | Huawei - moderator |
| R3-214159 | CB: # 25_MICO - Summary of email discussion | Nokia - moderator |
| R3-214160 | CB: # 26_SliceCorrections - Summary of email discussion | NTT Docomo - moderator |
| R3-214161 | CB: # 32_SONMDTCorrections - Summary of email discussion | ZTE - moderator |
| R3-214162 | CB: # 33_PositionCorrections - Summary of email discussion | Ericsson - moderator |
| R3-214163 | CB: # 34_DAPSCorrections - Summary of email discussion | Intel - moderator |
| R3-214164 | CB: # 35_IABCorrections - Summary of email discussion | Nokia - moderator |
| R3-214240 | Correction of maximum extended slice support items | NTT DOCOMO INC. |
| R3-214241 | Correction of inter system SON configuration Transfer | NTT DOCOMO INC. |
| R3-214242 | The NAS non delivery procedure is generalized. | Ericsson, CATT, Huawei, ZTE |
| R3-214246 | Correction to EN-DC definition in W1 | Huawei, China Unicom |
| R3-214252 | XnAP Slicing available capacity description alignment | Ericsson, China Unicom, Deutsche Telekom, CMCC, Verizon Wireless |
| R3-214253 | F1AP Slicing available capacity description alignment | Ericsson, China Unicom, Deutsche Telekom, CMCC, Verizon Wireless |
| R3-214254 | Dynamic ACL over NG CR 38.413 | Ericsson |
| R3-214255 | CB: # 104_PDUSessionDataForward - Summary of email discussion | NEC - moderator |
| R3-214256 | CB: # 105_NPNBroadcatsInfo - Summary of email discussion | Huawei - moderator |
| R3-214257 | CB: # 106_MultiPLMNClarification - Summary of email discussion | Nokia - moderator |
| R3-214258 | Missing QoS Flows not Admitted List in NGAP HANDOVER COMMAND | ZTE, Samsung, China Unicom, China Telecom, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-214259 | CB: # 108_CorrectionNGHO - Summary of email discussion | Nokia - moderator |
| R3-214260 | CB: # 109_NetworkInstance - Summary of email discussion | CATT - moderator |
| R3-214261 | Correction on EN-DC case | ZTE, Intel Corporation, Lenovo |
| R3-214262 | CB: # 111_XnSecurity - Summary of email discussion | Nokia - moderator |
| R3-214264 | Correction of NG Handover | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-214268 | Correction of served cell information for NPN | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-214269 | CB: # 113_GNBIDfailure - Summary of email discussion | Nokia - moderator |
| R3-214270 | CB: # 114_SecurityIndication - Summary of email discussion | China Telecom - moderator |
| R3-214271 | CB: # 115_F1-UDely - Summary of email discussion | Samsung - moderator |
| R3-214272 | Ignoring the notification Control for WWC | Huawei, BT |
| R3-214282 | Correction on NAS non delivery | ZTE, CATT, Huawei |
| R3-214288 | Correction of the RAN and LMF UE measurement IDs extension | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Inc. |
| R3-214302 | Adding procedural text for System Frame Number and Slot Number | Huawei, CMCC |
| R3-214303 | Adding procedural text for System Frame Number and Slot Number | Huawei, CMCC |
| R3-214311 | Correction of Broadcast PNI NPN | Nokia, Nokia Shanghai Bell |
| R3-214315 | Correction of NAS Non Delivery | Nokia, Nokia Shanghai Bell, Orange, CATT, Huawei, Ericsson, ZTE |
| R3-214316 | Correction of Xn Security | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-214317 | CB: # 33_PositionCorrections - Summary of email discussion | Ericsson - moderator |
| R3-214321 | Correction of Xn security capabilities | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-214322 | Correction of Xn security capabilities | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-214329 | Correction on NAS non delivery | ZTE, CATT, Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-214330 | NAS Non-Delivery | Huawei, CATT, Ericsson, ZTE, Nokia, Nokia Shanghai Bell |
| R3-214331 | The NAS non delivery procedure is generalized. | Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-214343 | Restricting the number of DL EHC contexts – Option 1 | Huawei, China Unicom, ZTE |
| R3-214360 | LS on inter-MN RRC resume without SN change | Qualcomm |
| R3-214361 | LS on UP security policy update by intra-cell handover | China Telecom |
| R3-214372 | LS on clarification of MICO mode | Nokia, Nokia Shanghai Bell |
| R3-214376 | Correction of PDU Session level Data Forwarding Information and QoS Flow list | NEC, Samsung, ZTE, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation |
| R3-214377 | Correction of PDU Session level Data Forwarding Information and QoS Flow list | NEC, Samsung, ZTE, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation |
| R3-214389 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-214390 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-214391 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-214392 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-214393 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-214394 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-214395 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom |
| R3-214396 | Correction of wrong CR implementation for Stage-3 CR on transmission stop for Rel-16 DAPS handover | Samsung, CATT, Intel Corporation |
| R3-214397 | CB: # 35_IABCorrections - Summary of email discussion | Nokia - moderator |
| R3-214403 | Support for handling unknown length of gNB identifier [FLEX_gNB_Len] | Qualcomm Incorporated, Huawei |
| R3-214404 | Support for handling unknown length of gNB identifier [FLEX_gNB_Len] | Qualcomm Incorporated, Huawei |
| R3-214406 | Correction CR on Network instance | CATT, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-214407 | Correction CR on Network instance | CATT, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-214410 | CB: # 111_XnSecurity - Summary of email discussion | Nokia - moderator |
| R3-214412 | Deactivation of the MICO mode indication | Huawei, Nokia, Nokia Shanghai-Bell, China Telecom |
| R3-214413 | Deactivation of the MICO mode indication | Huawei, Nokia, Nokia Shanghai-Bell, China Telecom |
| R3-214414 | LS On ACL support for Indirect Data Forwarding | Ericsson |
| R3-214433 | LS on downlink unmapped QoS flows | CATT |
| R3-214434 | Restricting the number of DL EHC contexts – Option 1 | Huawei, China Unicom, ZTE, Nokia, Nokia Shanghai Bell |
| R3-214435 | CB: # 22_EHC - Summary of email discussion | ZTE - moderator |
| R3-214441 | LS to SA3 on support of Pre-shared key derivation for IAB-donor-CU-UP | Huawei |
| R3-214442 | CB: # 21_UnmappedQoS - Summary of email discussion | CATT - moderator |
| R3-214443 | LS on downlink unmapped QoS flows | CATT |
| R3-214444 | CR on E1AP handling for unmapped DL flows | CATT, Intel Corporation, Huawei, China Telecom |
| R3-214453 | LS on downlink unmapped QoS flows | CATT |
| R3-214464 | LS on UP security policy update by intra-cell handover | China Telecom |
| R3-214465 | LS to SA3 on support of Pre-shared key derivation for IAB-donor-CU-UP | Huawei |
| R3-214467 | CB: # 23_InterMNResume_withoutSNChange - Summary of email discussion | Qualcomm - moderator |
| R3-214468 | CB: # 21_UnmappedQoS - Summary of email discussion | CATT - moderator |
| R3-214520 | Correction of RESOURCE STATUS UPDATE | Samsung, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, CATT, Huawei, CMCC |
| 9.3.4.2 | Pure Stage-2 Corrections | |
| R3-213103 | Clarification on RRC inactive to other RRC state transition procedure | Radisys |
| R3-213235 | Correction on the usage of SN Reconfiguration Complete | ZTE Corporation, Google, Intel Corporation, Lenovo, NEC |
| R3-213236 | Correction on the usage of SN Reconfiguration Complete in Rel-15 | ZTE Corporation, Google, Intel Corporation, Lenovo, NEC |
| R3-213237 | Correction on the usage of SN Reconfiguration Complete in Rel-16 | ZTE Corporation, Google, Intel Corporation, Lenovo, NEC |
| R3-213280 | DC in same and different DUs | NEC, ZTE, Google Inc. |
| R3-213309 | Corrections on the abbreviation of OAM | China Telecommunication |
| R3-213361 | RRC Re-establishment and inter-vendor CU operation | Ericsson, Verizon Wireless |
| R3-213362 | RRC Re-establishment and inter-vendor CU operation CR 38.401 | Ericsson, Verizon Wireless |
| R3-213363 | RRC Re-establishment and inter-vendor CU operation CR 38.401 | Ericsson, Verizon Wireless |
| R3-213375 | Suspend Configuration | Ericsson, Intel, CATT, Google |
| R3-213376 | Suspend Configuration | Ericsson, Intel, CATT, Google |
| R3-213515 | Clean-up on Xn-U Address Indication procedure | Intel Corporation, ZTE |
| R3-213516 | Clean-up on Xn-U Address Indication procedure | Intel Corporation, ZTE |
| R3-213572 | Correction on EN-DC messages | Huawei, China Unicom |
| R3-213573 | Correction on EN-DC messages | Huawei, China Unicom |
| R3-213957 | Correction on conditional reconfiguration for PSCell | Google Inc., Intel Corporation, CATT, ZTE |
| R3-214238 | DC in same and different DUs | NEC, ZTE, Google Inc., Nokia |
| R3-214265 | CB: # 112_Stage2Corrections - Summary of email discussion | NEC - moderator |
| R3-214266 | Clarification on RRC inactive to other RRC state transition procedure | Radisys, Reliance Jio |
| R3-214424 | Suspend Configuration | Ericsson, Intel, CATT, Google |
| 10.1 | General | |
| R3-213140 | BLCR to 36.423:Support of MDT enhancement | CATT |
| R3-213141 | BLCR to 38.413_Addition of SON features enhancement | Ericsson |
| R3-213142 | MDT in MR-DC | Huawei |
| R3-213143 | BLCR to 36.413_Addition of SON features enhancement | Qualcomm |
| R3-213146 | BLCR to 36.300_Addition of SON features enhancement | Lenovo, Motorola Mobility |
| R3-213149 | BLCR to 37.320: Support of MDT enhancement | Nokia, Nokia Shanghai Bell |
| R3-213157 | MRO for PScell Change Failure | Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE |
| R3-213158 | BLCR to 38.401_Addition of SON features enhancement | ZTE |
| R3-213159 | BLCR to 38.401: Support of MDT enhancement | CMCC |
| R3-213160 | BLCR to 36.423_Addition of SON features enhancement | CATT |
| R3-213161 | BLCR to 38.463: Support of MDT enhancement | Nokia, Nokia Shanghai Bell |
| R3-213162 | BLCR to 38.473: Support of MDT enhancement | Samsung |
| R3-213180 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-213181 | BLCR to 38.423_Addition of SON features enhancement | Samsung |
| R3-213182 | BLCR to 38.473_Addition of SON features enhancement | Huawei |
| R3-214118 | Updated work plan for enhancement of data collection for SON_MDT in NR and EN-DC WI | CMCC, Ericsson |
| R3-214165 | CB: # SONMDT1_Workplan_BLCRs - Summary of email discussion | CMCC - moderator |
| R3-214314 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-214505 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-214506 | BLCR to 38.401_Addition of SON features enhancement | ZTE |
| 10.2.1.3 | Successful Handover Report | |
| R3-213776 | Radio Link measurements for SHR candidate target cells optimization | InterDigital |
| R3-213811 | Successful Handover Report for CHO and DAPS | Ericsson, Interdigital |
| R3-214056 | Consideration on Successful Handover Report | ZTE |
| R3-214057 | (TP for SON BL CR for TS 38.413) Successful Handover support | ZTE |
| R3-214058 | (TP for SON BL CR for TS 38.423) Successful Handover support | ZTE |
| R3-214059 | (TP for SON BL CR for TS 38.473) Successful Handover support | ZTE |
| R3-214060 | [Draft]LS on information from UE for Successful Handover Report | ZTE |
| R3-214166 | CB: # SONMDT2_SuccessHO - Summary of email discussion | InterDigital - moderator |
| 10.2.1.4 | UE History Information in EN-DC | |
| R3-213281 | Further discussion on UE History Information (UHI) in MR-DC | NEC |
| R3-213307 | Discussion on UE history information | China Telecommunication |
| R3-213385 | Discussion on 2-dimentional structure for the SCG UHI | Nokia, Nokia Shanghai Bell |
| R3-213386 | (TP to SON BL CR to 38.423, NR_ENDC_SON_MDT_enh-Core) Enabling SCG UHI | Nokia, Nokia Shanghai Bell |
| R3-213387 | (TP to SON BL CR to 36.423, NR_ENDC_SON_MDT_enh-Core) Enabling SCG UHI | Nokia, Nokia Shanghai Bell |
| R3-213404 | (TP for SON BLCR for 38.423) UE History Information in MR-DC | Huawei |
| R3-213405 | (TP for SON BLCR for 38.413) UE History Information in MR-DC | Huawei |
| R3-213406 | (TP for SON BLCR for 36.413 and 36.423) UE History Information in EN-DC | Huawei |
| R3-213502 | Enhancement of UE history information in MR-DC scenario | CATT,CMCC |
| R3-213503 | (TP on UE history information for 36.413) Addition of UE history information for SN | CATT,CMCC |
| R3-213504 | (TP on UE history information for 36.423) Addition of UE history information for SN | CATT,CMCC |
| R3-213658 | UE History Information in MR-DC | Qualcomm Incorporated |
| R3-213812 | (TP for SON BL CR for TS 38.423) UE History Information for Secondary Node | Ericsson |
| R3-214010 | UE History Information in MR-DC | Samsung |
| R3-214011 | TP for SON BLCR for 36.423: UE History Information in EN-DC | Samsung |
| R3-214012 | TP for SON BLCR for 38.423: UE History Information in MR-DC | Samsung |
| R3-214061 | UE History Information in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-214062 | (TP for SON BL CR for TS 37.340) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-214063 | (TP for SON BL CR for TS 36.423) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-214064 | (TP for SON BL CR for TS 38.413) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-214065 | (TP for SON BL CR for TS 38.423) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-214122 | (TP to SON BLCR TS 38.413)UE history information in MR-DC | CMCC, CATT |
| R3-214123 | (TP to SON BLCR TS 38.423)UE history information in MR-DC | CMCC, CATT |
| R3-214167 | CB: # SONMDT3_UEHistoryInfor - Summary of email discussion | ZTE - moderator |
| R3-214318 | CB: # SONMDT3_UEHistoryInfor - Summary of email discussion | ZTE - moderator |
| R3-214469 | CB: # SONMDT3_UEHistoryInfor - Summary of email discussion | ZTE - moderator |
| 10.2.1.5 | Load Balancing Enhancements | |
| R3-213286 | PRB per slice reporting: proposed resolution to FFS | NEC |
| R3-213287 | (TP for SON BLCR for 38.423) Load Balancing Enhancements: SUL reporting in Composite Available Capacity message | NEC |
| R3-213288 | (TP for SON BLCR for 38.473) Load Balancing Enhancements: SUL reporting in Composite Available Capacity message | NEC |
| R3-213289 | (TP for SON BLCR for 38.423) Load Balancing Enhancements: SUL reporting in Radio Resource Status message | NEC |
| R3-213290 | (TP for SON BLCR for 38.473) Load Balancing Enhancements: SUL reporting in Radio Resource Status message | NEC |
| R3-213388 | Consideration on the CU-DU impacts of the per-beam mobility setting change | Nokia, Nokia Shanghai Bell |
| R3-213389 | (TP to SON BL CR to 38.473, NR_ENDC_SON_MDT_enh-Core) Enabling CU-DU information exchange to support per-beam mobility setting change | Nokia, Nokia Shanghai Bell |
| R3-213390 | Completion of the solution for per-slice PRB reporting | Nokia, Nokia Shanghai Bell |
| R3-213391 | (TP to SON BL CR to 38.423, NR_ENDC_SON_MDT_enh-Core) Removal of the FFS related to the per-slice PRB reporting | Nokia, Nokia Shanghai Bell |
| R3-213407 | (TP for SON BLCR for 38.423) Load Balancing Enhancements | Huawei |
| R3-213510 | Discussion on PSCell MLB | CATT |
| R3-213511 | (TP on SON for 36.423) TP on PSCell MLB | CATT |
| R3-213815 | (TP for SON BL CR for TS 38.423) MLB enhancements | Ericsson |
| R3-213816 | (TP for SON BL CR for TS 36.423) MLB enhancements | Ericsson |
| R3-214089 | Discussion on Number of Inactive UE | ZTE |
| R3-214090 | Discussion on Number of Inactive UE | ZTE |
| R3-214091 | Discussion on Number of Inactive UE | ZTE |
| R3-214092 | Discussion on Number of Inactive UE | ZTE |
| R3-214103 | Further discussions on load metric | CMCC |
| R3-214104 | TP to SON BLCR 38.300 on MLB | CMCC |
| R3-214168 | CB: # SONMDT4_LoadBalance - Summary of email discussion | CMCC - moderator |
| R3-214319 | TP to SON BLCR 38.300 on MLB | CMCC, ZTE |
| R3-214320 | CB: # SONMDT4_LoadBalance - Summary of email discussion | CMCC - moderator |
| 10.2.1.6 | MRO for SN Change Failure | |
| R3-213308 | Discussion on MRO for SN Change Failure | China Telecommunication |
| R3-213392 | MRO for PSCell change failure | Nokia, Nokia Shanghai Bell |
| R3-213393 | (TP to SON BL CR to 38.423, NR_ENDC_SON_MDT_enh-Core) Enabling SCG MRO | Nokia, Nokia Shanghai Bell |
| R3-213394 | (TP to SON BL CR to 36.423, NR_ENDC_SON_MDT_enh-Core) Enabling SCG MRO | Nokia, Nokia Shanghai Bell |
| R3-213408 | (TP for SON BLCR for 38.423) MRO for SN Change Failure | Huawei |
| R3-213409 | (TP for SON BLCR for 38.300) MRO for SN Change Failure | Huawei |
| R3-213500 | Consideration on support of SN change failure in case of MR-DC | CATT |
| R3-213501 | (TP on SN change failure for 38.423) Addition of SCG Failure procedure for SN change failure | CATT |
| R3-213659 | MRO for SN Change Failure | Qualcomm Incorporated |
| R3-213817 | (TP for SON BL CR for TS 38.473) MRO for SN Change Failure | Ericsson |
| R3-214001 | Further consideration on MRO SN change failure | ZTE |
| R3-214002 | (TP for SON BL CR for TS 38.423) MRO SN change failure | ZTE |
| R3-214008 | Support of SN change failure | Samsung |
| R3-214009 | TP for SON BLCR for 38.423: Support of SN change failure | Samsung |
| R3-214169 | CB: # SONMDT5_MROSNchange - Summary of email discussion | Samsung - moderator |
| R3-214332 | CB: # SONMDT5_MROSNchange - Summary of email discussion | Samsung - moderator |
| 10.2.1.7 | RACH Optimization Enhancements | |
| R3-213217 | (TP for SON BL CR for TS 38.473): Left overs on RACH Optimization Enhancements | Huawei |
| R3-213218 | (TP for SON BL CR for TS 38.401):Stage 2 update for RACH Optimization | Huawei |
| R3-213219 | UE RACH report for SN | Huawei |
| R3-213507 | Discussion on Rel-16 leftover issues for PRACH coordination | CATT |
| R3-213508 | (TP on SON for 38.473) TP on PRACH coordination for F1AP | CATT |
| R3-213509 | (TP on SON for 36.423) TP on PRACH coordination for X2AP | CATT |
| R3-213662 | PRACH conflict detection and resolution | NEC |
| R3-213689 | Down-selection and open point for RACH optimization | Nokia, Nokia Shanghai Bell |
| R3-213690 | (TP for SON BL CR to TS 38.473) Enhancement of RACH Conflict Resolution | Nokia, Nokia Shanghai Bell |
| R3-213818 | Signaling solution for Beam Sweeping Reconfiguration from gNB-DU to the gNB-CU | Ericsson |
| R3-213819 | (TP for SON BL CR for TS38.473) RACH conflict resolution and RACH report availability indication over F1 interface | Ericsson |
| R3-214170 | CB: # SONMDT6_RACHOpt - Summary of email discussion | CATT - moderator |
| R3-214333 | CB: # SONMDT6_RACHOpt - Summary of email discussion | CATT - moderator |
| 10.2.2 | Coverage and Capacity Optimization | |
| R3-213291 | CCO over F1: functional split and signaling between gNB-CU and gNB-DU | NEC |
| R3-213292 | (TP for SON BLCR 38.300) Coverage and Capacity Optimization | NEC |
| R3-213293 | (TP for SON BLCR for 38.473) Coverage and Capacity Optimization | NEC |
| R3-213410 | (TP for SON BLCR for 38.473) Coverage and Capacity Optimization | Huawei |
| R3-213604 | (TP for SON BLCR for 38.401,38.300) Coverage and Capacity Optimization | Huawei |
| R3-213605 | Coverage and Capacity Optimization | Huawei |
| R3-213660 | Coverage and Capacity Optimization | Qualcomm Incorporated |
| R3-213687 | Coverage aspect of NR CCO | Nokia, Nokia Shanghai Bell |
| R3-213820 | Inter-gNB CCO | Ericsson |
| R3-213821 | (TP for SON BL CR for TS 38.300) Intra-gNB CCO | Ericsson |
| R3-213822 | (TP for SON BL CR for TS 38.423) CCO | Ericsson |
| R3-213823 | (TP for SON BL CR for TS 38.473) CCO | Ericsson |
| R3-214006 | Support of CCO | Samsung |
| R3-214007 | TP for SON BLCR for 38.300: Support of CCO | Samsung |
| R3-214035 | Further Discussion on Coverage and Capacity Optimization in NR | ZTE, China Telecom, China Unicom |
| R3-214036 | Draft LS on OAM Configuration for Coverage and Capacity Optimization | ZTE |
| R3-214037 | TP for BL CR 38.300 on Coverage and Capacity Optimization | ZTE, China Telecom, China Unicom |
| R3-214038 | TP for BL CR 38.423 on Coverage and Capacity Optimization | ZTE, China Telecom, China Unicom |
| R3-214039 | TP for BL CR 38.473 on Coverage and Capacity Optimization | ZTE, China Telecom, China Unicom |
| R3-214171 | CB: # SONMDT7_CCO - Summary of email discussion | Ericsson - moderator |
| R3-214323 | CB: # SONMDT7_CCO - Summary of email discussion | Ericsson - moderator |
| 10.2.4 | Inter-System Load Balancing | |
| R3-213411 | (TP for SON BLCR for 38.413) Inter-System Load Balancing | Huawei |
| R3-213824 | (TP for SON for TS 38.413, TS 38.300, TS 36.300) Inter-System Load Balancing | Ericsson |
| R3-214055 | Further Discussion on Inter-system Load Balancing in NR | ZTE, China Telecom, China Unicom |
| R3-214066 | TP for BL CR 36.300 on Inter-system Load Balancing | ZTE, China Telecom, China Unicom |
| R3-214083 | TP for BL CR 38.300 on Inter-system Load Balancing | ZTE, China Telecom, China Unicom |
| R3-214084 | TP for BL CR 38.413 on Inter-system Load Balancing | ZTE, China Telecom, China Unicom |
| R3-214105 | Further discussions on inter-system load balancing | CMCC |
| R3-214106 | TP to SON BLCR 36.300 for inter-system load balancing | CMCC |
| R3-214107 | TP to SON BLCR 38.300 for inter-system load balancing | CMCC |
| R3-214172 | CB: # SONMDT8_InterSystemLB - Summary of email discussion | Huawei - moderator |
| R3-214267 | (TP for SON for TS 38.413, TS 38.300, TS 36.300) Inter-System Load Balancing | Ericsson |
| R3-214324 | CB: # SONMDT8_InterSystemLB - Summary of email discussion | Huawei - moderator |
| 10.2.6 | Mobility Enhancement Optimization | |
| R3-213412 | (TP for SON BLCR for 38.300) Mobility Enhancement Optimization | Huawei |
| R3-213497 | Discussion on MRO for CHO mobility enhance | CATT |
| R3-213498 | (TP on MRO for 38.423) Failure Indication message enhancement for CHO | CATT |
| R3-213499 | Discussion on MRO for DAPS mobility enhance | CATT |
| R3-213719 | SON Enhancements for CHO | Lenovo, Motorola Mobility, ZTE |
| R3-213720 | SON Enhancements for DAPS Handover | Lenovo, Motorola Mobility, ZTE |
| R3-213721 | Update of Way forward on Scenarios for SON enhancements for CHO and DAPS HO | Lenovo, Motorola Mobility |
| R3-213813 | (TP for SON BL CR for TS 38.300) DAPS handover SON aspects | Ericsson |
| R3-213814 | (TP for SON BL CR for TS 38.300) Mobility Robustness Optimization for Conditional Handover | Ericsson |
| R3-213926 | Discussion of stage 3 impact on SON enhancements for CHO | Samsung |
| R3-213927 | TP for TS38.300: SON enhancements for CHO | Samsung |
| R3-213928 | TP for SON BLCR for 38.423: Support of CHO for MRO | Samsung |
| R3-213977 | Discussion on SON enhancements for CHO | Samsung |
| R3-214003 | Consideration on Mobility enhancement | ZTE |
| R3-214116 | Remaining issues on SON Enhancement for CHO. | CMCC |
| R3-214117 | Remaining issues on SON Enhancement for DAPS | CMCC |
| R3-214173 | CB: # SONMDT9_CHODAPSEnh - Summary of email discussion | Lenovo - moderato |
| R3-214325 | CB: # SONMDT9_CHODAPSEnh - Summary of email discussion | Lenovo - moderato |
| R3-214432 | Update of Way forward on Scenarios for SON enhancements for CHO and DAPS HO | Lenovo, Motorola Mobility |
| 10.3.2.1 | MDT Enhancements | |
| R3-213220 | (TPs for MDT BL CRs for TS 38.473, TS 37.320): Discussion on propagation of user consent related information during Xn inter-PLMN handover | Huawei |
| R3-213221 | Propagation of user consent related information during Xn inter-PLMN handover | Huawei |
| R3-213506 | Propagation of immediate MDT configuration in case of Xn inter-RAT HO | CATT |
| R3-213704 | Propagation for Management Based MDT PLMN List | Samsung |
| R3-213705 | Propagation for Management Based MDT PLMN List | Samsung |
| R3-213806 | Left issue for MDT enhancement | ZTE |
| R3-213826 | (TP for MDT BL CR for TS 38.413, TS38.423) TPs for the introduction of the on Beam level measurement report configuration | Ericsson |
| R3-213827 | [DRAFT] LS on the Beam measurement reports for the MDT measurements | Ericsson |
| R3-214174 | CB: # SONMDT10_MDTEnh - Summary of email discussion | ZTE - moderator |
| R3-214348 | (TPs for MDT BL CRs for TS 38.423): Discussion on propagation of user consent related information during Xn inter-PLMN handover | Huawei |
| R3-214349 | (TPs for MDT BL CRs for TS 37.320): Discussion on propagation of user consent related information during Xn inter-PLMN handover | Huawei |
| R3-214350 | Propagation of user consent related information during Xn inter-PLMN handover | Huawei, Samsung |
| R3-214452 | Propagation of user consent related information during Xn inter-PLMN handover | Huawei, Samsung, Ericsson |
| R3-214463 | LS on the Beam measurement reports for the MDT measurements | Ericsson |
| R3-214475 | LS on the Beam measurement reports for the MDT measurements | Ericsson |
| R3-214519 | LS on the Beam measurement reports for the MDT measurements | Ericsson |
| 10.3.2.2 | MDT for MR-DC | |
| R3-213222 | (TP for MDT BLCR for TS 38.413): MDT for MR-DC | Huawei |
| R3-213688 | Inter-node coordination for MDT in case of MR-DC | Nokia, Nokia Shanghai Bell |
| R3-213807 | MDT for MR-DC | ZTE |
| R3-213808 | (TP for 38.423) MDT for MR-DC | ZTE |
| R3-213825 | Discussion on multiple MDT configurations for NR-DC | Ericsson |
| R3-214175 | CB: # SONMDT11_MDTforMRDC - Summary of email discussion | Nokia - moderator |
| R3-214326 | CB: # SONMDT11_MDTforMRDC - Summary of email discussion | Nokia - moderator |
| 10.4 | Support for L2 Measurements | |
| R3-213223 | L2 measurement in MR-DC | Huawei |
| R3-213809 | Average delay DL on F1-U for M6 measurement | ZTE |
| R3-213828 | Discussion on L2 Measurements | Ericsson |
| R3-214176 | CB: # SONMDT12_L2Measurements - Summary of email discussion | Huawei - moderator |
| R3-214313 | MDT M6 calculation for split bearers in MR-DC | Huawei |
| R3-214327 | CB: # SONMDT12_L2Measurements - Summary of email discussion | Huawei - moderator |
| R3-214466 | MDT M6 calculation for split bearers in MR-DC | Huawei |
| 10.5 | SON/MDT Optimizations for NR-U | |
| R3-213224 | SON for NR-U | Huawei |
| R3-213395 | Load information enhancements for NR-U | Nokia, Nokia Shanghai Bell |
| R3-213505 | Discussion on MRO for NR-U | CATT |
| R3-213722 | SON enhancements for NR-U | Lenovo, Motorola Mobility |
| R3-213829 | Further details on proposals on MLB for NR-U | Ericsson |
| R3-213896 | Load information for NR-U | Charter Communications, Inc |
| R3-214093 | Discussion on Load Balancing Optimization for NR-U | ZTE |
| R3-214177 | CB: # SONMDT13_NRU_LB - Summary of email discussion | Ericsson - moderator |
| R3-214328 | CB: # SONMDT13_NRU_LB - Summary of email discussion | Ericsson - moderator |
| 11.1 | General | |
| R3-213114 | LS on the coordination between gNBs on the supporting of RedCap UEs | RAN2 |
| R3-213267 | Access Restriction for RedCap Ues | Qualcomm Incorporated |
| R3-213268 | [DRAFT] Reply LS on the coordination between gNBs on the supporting of RedCap Ues | Qualcomm Incorporated |
| R3-213351 | Coordination between gNBs on the supporting of RedCap UEs | Huawei |
| R3-213352 | [DRAFT] Reply on the coordination between gNBs on the supporting of RedCap Ues | Huawei |
| R3-213353 | Supporting RedCap UEs over NG interface | Huawei |
| R3-213354 | Supporting RedCap UEs over Xn interface | Huawei |
| R3-213521 | Discussion on mobility restriction for RedCap UEs | NTT DOCOMO INC. |
| R3-213836 | Discussion on the gNB coordination aspect for restricting RedCap UE access during Handover | Ericsson |
| R3-213837 | [Draft] Reply LS on the coordination between gNBs on the supporting of RedCap Ues | Ericsson |
| R3-213844 | WI work plan for RedCap | Ericsson |
| R3-213972 | RedCap capability exchange | Samsung |
| R3-214016 | Discussion and Draft Reply LS for RedCap | ZTE |
| R3-214031 | Inter-node Coordination for RedCap over Xn | ZTE |
| R3-214032 | Inter-node Coordination for RedCap over F1 | ZTE |
| R3-214147 | CB: # RedCap1_Workplan_LSin - Summary of email discussion | Ericsson - moderator |
| R3-214422 | Reply LS on the coordination between gNBs on the supporting of RedCap Ues | Ericsson |
| 11.2 | Support for the Extended DRX enhancements for RedCap UEs | |
| R3-213332 | Discussion on the LSin about RedCap | CATT |
| R3-213349 | General Analysis of RedCap | Huawei |
| R3-213350 | Supporting RedCap UEs over F1 interface | Huawei |
| R3-213451 | Support of UEs with reduced capability | Nokia, Nokia Shanghai Bell |
| R3-213452 | Support of UEs with reduced capability | Nokia, Nokia Shanghai Bell |
| R3-213698 | Discussion on additional RAN3 issues for RedCap | Samsung |
| R3-213845 | Discussion on RAN3 impacts to support NR RedCap UE | Ericsson |
| R3-213846 | Draft BL CR to NG-AP: Support of RedCap eDRX information | Ericsson |
| R3-214033 | Discussion on eDRX of RedCap | ZTE |
| R3-214034 | Introduction of RedCap eDRX over NGAP | ZTE |
| R3-214101 | Discussion on Extended DRX enhancements for RedCap Ues | CMCC |
| R3-214148 | CB: # RedCap2_eDRX - Summary of email discussion | Nokia - moderator |
| 12.1 | General | |
| R3-213574 | Work plan of Rel-17 enhancements for NB-IoT and LTE-MTC | Huawei, Ericsson |
| R3-214178 | CB: # NBIoTMTC1_WorkPlan - Summary of email discussion | Huawei - moderator |
| 12.2 | Support for Carrier Selection and Carrier Specific Configuration | |
| R3-213244 | Discussion on Carrier Selection and Carrier Specific Configuration | ZTE |
| R3-213245 | 36.413 (Rel-17) Introduction of CEL based paging carrier selection | ZTE |
| R3-213246 | 38.413 (Rel-17) Introduction of CEL based paging carrier selection | ZTE |
| R3-213453 | Support of Carrier Selection based on coverage level | Nokia, Nokia Shanghai Bell |
| R3-213454 | Support of Carrier Selection based on coverage level | Nokia, Nokia Shanghai Bell |
| R3-213575 | Consideration on Carrier Selection and Carrier Specific Configuration | Huawei |
| R3-213576 | Support of CE based carrier selection | Huawei |
| R3-213850 | Discussion on Rel-17 eMTC/NB-IoT RAN3 impacts | Ericsson |
| R3-213978 | Support of CE based carrier selection | Huawei |
| R3-214179 | CB: # NBIoTMTC2_CarrierSelection - Summary of email discussion | Nokia - moderator |
| 13.1 | General | |
| R3-213155 | BL CR to XnAP on Rel-17 eIAB | Samsung, Nokia, Nokia Shanghai Bell, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics |
| R3-213156 | CR on CP-UP separation for Rel-17 IAB | Nokia, Nokia Shanghai Bell, Samsung, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics |
| R3-213171 | CP-based Congestion Mitigation for IAB Network | ZTE |
| R3-213178 | BL CR to TS 38.401 on support of eIAB | Huawei |
| R3-213186 | CP-based Congestion Indication for IAB Networks | Ericsson |
| R3-213255 | Updated Workplan for Rel-17 IAB | Qualcomm Incorporated (WI Rapporteur) |
| R3-214231 | CB: # 1301_IAB_BL_CRs - Summary of email discussion | Qualcomm - moderator |
| R3-214507 | BL CR to TS 38.401 on support of eIAB | Huawei |
| 13.2.1.1 | Procedure Details | |
| R3-213205 | Discussion on inter-donor migration in IAB | ZTE |
| R3-213256 | Inter-donor topology adaptation procedures | Qualcomm Incorporated |
| R3-213313 | (TP for IAB BL CR TS38.401) Discussion on inter-donor IAB node migration procedure for Rel-17 eIAB | Samsung |
| R3-213326 | Inter-Donor IAB Node Migration (Procedure Details) | CATT |
| R3-213486 | Procedure of full migration | Fujitsu |
| R3-213530 | discussion on Inter-Donor IAB Node Migration | Nokia, Nokia Shanghai Bell |
| R3-213598 | IAB Inter-donor Topology Adaptation | Ericsson |
| R3-213691 | Remaining issues for IAB inter-donor migration | Lenovo, Motorola Mobility |
| R3-213932 | (TP for NR_IAB_enh BL CR for TS 38.401) Inter-CU topology update | Huawei |
| R3-214230 | response to R3-213313 and R3-213326 | Nokia, Nokia Shanghai Bell |
| R3-214232 | CB: # 1302_IAB_Inter_Donor_Mig - Summary of email discussion | Ericsson - moderator |
| R3-214366 | CB: # 1302_IAB_Inter_Donor_Mig - Summary of email discussion | Ericsson - moderator |
| R3-214448 | CB: # 1302_IAB_Inter_Donor_Mig - Summary of email discussion | Ericsson - moderator |
| R3-214449 | LS to RAN2 capturing the agreements so far on BAP | Ericsson |
| R3-214474 | LS on BAP- and RRC-related agreements from RAN3#113-e | Ericsson |
| R3-214476 | LS on BAP- and RRC-related agreements from RAN3#113-e | Ericsson |
| 13.2.1.2 | CHO and DAPS | |
| R3-213327 | Inter-Donor IAB Node Migration (CHO) | CATT |
| R3-213487 | Handling of descendant nodes in inter-donor CHO and RLF recovery | Fujitsu |
| R3-213599 | The Discussion Status in AI 13.2.1.2 | Ericsson |
| 13.2.2 | Reduction of Service Interruption | |
| R3-213132 | Reply LS to LS Usage of MOBIKE in IAB | SA3 |
| R3-213206 | Further considerations on service interruption reduction | ZTE |
| R3-213257 | Reduction of service interruption during IAB migration | Qualcomm Incorporated |
| R3-213531 | Discussion on unnecessary UL/DL transmission during Intra-Donor Topology Adaptation | Nokia, Nokia Shanghai Bell |
| R3-213600 | Mitigation of Unnecessary DL and UL Transmissions During Intra-Donor Topology Adaptation | Ericsson |
| R3-213699 | Discussion on Service Interruption Reduction for Rel-17 IAB | Samsung |
| R3-213933 | Reduction of Service Interruption for IAB topology update | Huawei |
| R3-214233 | CB: # 1303_IAB_Red_Serv_Inter - Summary of email discussion | Samsung - moderator |
| R3-214340 | (TP for BL CR for TS 38.401) add MOBIKE in Stage-2 | Nokia, Nokia Shanghai Bell |
| R3-214367 | CB: # 1303_IAB_Red_Serv_Inter - Summary of email discussion | Samsung - moderator |
| R3-214398 | (TP for BL CR for TS 38.401) add MOBIKE in Stage-2 | Nokia, Nokia Shanghai Bell |
| 13.2.3 | Topology Redundancy | |
| R3-213123 | LS on Topology Adaptation enhancements | RAN2 |
| R3-213207 | Discussion on Inter-topology routing in redundancy scenario | ZTE |
| R3-213258 | Inter-donor topology transport | Qualcomm Incorporated |
| R3-213312 | (TP for IAB BL CR TS38.401) Discussion on topology redundancy for Rel-17 IAB | Samsung |
| R3-213328 | CP-UP separation and inter-donor topology redundancy | CATT |
| R3-213488 | Discussion on the inter-donor topology redundancy | Fujitsu |
| R3-213532 | discussion on Inter-CU topology redundancy | Nokia, Nokia Shanghai Bell |
| R3-213692 | Discussion on IAB inter-donor topology redundancy | Lenovo, Motorola Mobility |
| R3-213934 | Inter-CU topology redundancy | Huawei |
| R3-214234 | CB: # 1304_IAB_Top_Red - Summary of email discussion | Qualcomm - moderator |
| R3-214368 | CB: # 1304_IAB_Top_Red - Summary of email discussion | Qualcomm - moderator |
| 13.3.1 | Congestion Mitigation | |
| R3-213210 | (TP for NR_IAB_enh BL CR for TS 38.473): Congestion indication in CP-based congestion mitigation | ZTE |
| R3-213329 | Congestion Mitigation for CP-based | CATT |
| R3-213533 | (TP for IAB BLCR 38.473) C-plane congestion indication per Routing ID | Nokia, Nokia Shanghai Bell |
| R3-213601 | (TP for IAB BL CR for TS 38.473): Congestion Mitigation in IAB Networks | Ericsson |
| R3-213935 | Discussion on IAB congestion mitigation | Huawei |
| R3-214235 | CB: # 1305_IAB_Con_Mit - Summary of email discussion | Huawei - moderator |
| R3-214369 | CB: # 1305_IAB_Con_Mit - Summary of email discussion | Huawei - moderator |
| 13.3.2 | Multi-Hop Performance: QoS, Latency, Fairness | |
| R3-213208 | Discussion on inter-Donor-DU re-routing in IAB | ZTE |
| R3-213259 | Inter-donor-DU local rerouting for IAB | Qualcomm Incorporated |
| R3-213330 | Inter-donor-DU re-routing | CATT |
| R3-213534 | Inter donor-DU re-routing | Nokia, Nokia Shanghai Bell |
| R3-213602 | The avoidance of UL Packet Discarding due to Local Re-routing | Ericsson |
| R3-213693 | Discussion on UL packet discarding for inter-donor-DU re-routing | Lenovo, Motorola Mobility |
| R3-213700 | Discussion on inter-donor-DU rerouting for Rel-17 IAB | Samsung |
| R3-213936 | Inter-donor re-routing for IAB and unnecessary transmission during topology update | Huawei |
| R3-214236 | CB: # 1306_IAB_Multi-hop - Summary of email discussion | ZTE - moderator |
| R3-214370 | CB: # 1306_IAB_Multi-hop - Summary of email discussion | ZTE - moderator |
| 13.4.1 | Resource Multiplexing of Child and Parent Links and CLI Management | |
| R3-213209 | Discussion on resource multiplexing in IAB | ZTE |
| R3-213535 | Resource multiplexing | Nokia, Nokia Shanghai Bell |
| R3-213603 | Inter-donor Resource Coordination in IAB Networks | Ericsson |
| R3-213937 | (TP for NR_IAB_enh BL CR for TS 38.423) IAB resource multiplexing | Huawei |
| R3-214237 | CB: # 1307_IAB_Res_Multiplex - Summary of email discussion | Nokia - moderator |
| R3-214371 | CB: # 1307_IAB_Res_Multiplex - Summary of email discussion | Nokia - moderator |
| 14.1 | General | |
| R3-213163 | CPAC BL CR to TS38.401 | ZTE |
| R3-213184 | SCG BL CR to TS 37.340 | ZTE |
| R3-213185 | SCG BL CR to TS 38.401 | Huawei |
| R3-213187 | SCG BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-213188 | SCG BL CR to TS 38.423 | Ericsson |
| R3-213189 | SCG BL CR to TS 38.473 | Samsung |
| R3-213190 | CPAC BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-213191 | CPAC BL CR to TS 37.340 | Huawei |
| R3-213192 | CPAC BL CR to TS 38.423 | Ericsson |
| R3-213193 | CPAC BL CR to TS 36.420 | China Telecom |
| R3-213380 | (TP to CPAC BL CR to 36.423, LTE_NR_DC_enh2-Core) CPAC BL CR correction | Nokia, Nokia Shanghai Bell |
| R3-213943 | BLCR to TS 38.473 for Conditional PScell Change/Addition | CATT |
| R3-214180 | CB: # MRDC1_BLCRs - Summary of email discussion | Samsung - moderator |
| R3-214277 | SCG BL CR to TS 38.473 | Samsung |
| R3-214278 | BLCR to TS 38.473 for Conditional PScell Change/Addition | CATT |
| R3-214279 | CPAC BL CR to TS 36.420 | China Telecom |
| R3-214280 | SCG BL CR to TS 37.340 | ZTE |
| R3-214485 | CPAC BL CR to TS 38.473 | CATT |
| R3-214491 | SCG BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-214492 | SCG BL CR to TS 37.340 | ZTE |
| R3-214493 | SCG BL CR to TS 38.401 | Huawei |
| R3-214494 | SCG BL CR to TS 38.423 | Ericsson |
| R3-214495 | SCG BL CR to TS 38.473 | Samsung |
| R3-214496 | CPAC BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-214497 | CPAC BL CR to TS 37.340 | Huawei |
| R3-214498 | CPAC BL CR to TS38.401 | ZTE |
| R3-214499 | CPAC BL CR to TS 38.423 | Ericsson |
| R3-214500 | CPAC BL CR to TS38.463 | Qualcomm |
| R3-214501 | BLCR to TS 38.473 for Conditional PScell Change/Addition | CATT |
| 14.2 | Signaling Support for Efficient Activation/Deactivation for One SCG and SCells | |
| R3-213215 | TP for SCG BL CR to TS37.340 | ZTE |
| R3-213216 | TP for SCG BL CR to TS38.423 36.423 38.473 38.463 | ZTE |
| R3-213282 | (TP for SCG BL CR to TS36.423) Acceptance / Rejection of SCG Activation / Deactivation | NEC |
| R3-213283 | SCG Activation / deactivation discussion on E1 | NEC |
| R3-213368 | Aspects of SCG deactivation/activation | Qualcomm Incorporated |
| R3-213381 | (TP to SCG BL CR to 38.423, LTE_NR_DC_enh2-Core) Completion of the solution for the SCG activation state change | Nokia, Nokia Shanghai Bell |
| R3-213382 | (TP to SCG BL CR to 36.423, LTE_NR_DC_enh2-Core) Completion of the solution for the SCG activation state change | Nokia, Nokia Shanghai Bell |
| R3-213563 | (TP to 38.401 SCG BL CR) SCG activation and deactivation | Huawei |
| R3-213564 | (TP to 38.463 SCG BL CR) SCG activation and deactivation | Huawei |
| R3-213661 | Open Issues on Activation/Deactivation for One SCG and SCells | LG Electronics |
| R3-213701 | (TP to SCG BL CR TS38.473) Discussion on SCG activation and deactivation | Samsung |
| R3-213716 | Support of SCG Activation and Deactivation | Lenovo, Motorola Mobility |
| R3-213717 | Remaining issues on SCG activation and deactivation | Lenovo, Motorola Mobility |
| R3-213868 | (TP for SCG BL CR to TS 36.423) Feedback for SCG (de)activation | Ericsson |
| R3-213869 | (TP for SCG BL CR to TS 38.423) Feedback for SCG (de)activation | Ericsson |
| R3-213940 | Discussion on efficient Activation/Deactivation for SCG | CATT |
| R3-213941 | (TP for [LTE_NR_DC_enh2-Core] SCG BLCR for TS 38423) efficient Activation/Deactivation for SCG | CATT |
| R3-214181 | CB: # MRDC2_SCGActivation_Deactivation - Summary of email discussion | ZTE - moderator |
| R3-214298 | CB: # MRDC2_SCGActivation_Deactivation - Summary of email discussion | ZTE - moderator |
| R3-214399 | (TP to 38.401 SCG BL CR) SCG activation and deactivation | Huawei |
| R3-214419 | TP for SCG BL CR to TS37.340 | ZTE |
| R3-214421 | (TP to SCG BL CR TS38.473) Discussion on SCG activation and deactivation | Samsung |
| R3-214428 | (TP for SCG BL CR to TS 38.423) Feedback for SCG (de)activation | Ericsson |
| R3-214445 | (TP to SCG BL CR to 36.423, LTE_NR_DC_enh2-Core) Completion of the solution for the SCG activation state change | Nokia, Nokia Shanghai Bell |
| R3-214451 | (TP for SCG BL CR to TS 38.423) Feedback for SCG (de)activation | Ericsson |
| 14.3 | Signaling Support for Conditional PSCell Change/Addition | |
| R3-213212 | (TP for CPAC BL CR to TS36.423) Enhance Early Status Transfer message for CPA | ZTE |
| R3-213213 | (TP for CPAC BL CR to TS38.423) Enhance Early Status Transfer message for CPA | ZTE |
| R3-213214 | (TP for CPAC BL CR to TS 37.340) Clarification on Early Data Forwarding | ZTE |
| R3-213238 | (TP for CPAC BLCR to TS36.423) Data forwarding for EN-DC | ZTE |
| R3-213239 | (TP for CPAC BLCR to TS38.423) Data forwarding for MR-DC with 5GC | ZTE |
| R3-213284 | (TP for CPAC BL CR to TS 36.423 ) Discussion on CPAC (Conditional PSCell Addition and PSCell Change) | NEC |
| R3-213285 | (TP for CPAC BL CR to TS 38.423 ) Discussion on CPAC (Conditional PSCell Addition and PSCell Change) | NEC |
| R3-213304 | Discussion on Conditional PScell Addition/Change procedures | China Telecommunication |
| R3-213305 | TP on 36.423 for introducing CPAC information in SgNB Addition procedure | China Telecommunication |
| R3-213306 | TP on 38.423 for introducing CPAC information in SN Addition procedure | China Telecommunication |
| R3-213366 | CPAC replace procedures | Qualcomm Incorporated |
| R3-213367 | CPA and Inter-SN CPC: preparation, execution, and data forwarding | Qualcomm Incorporated |
| R3-213383 | (TP to CPAC BL CR to 38.423, LTE_NR_DC_enh2-Core) Max number of PSCells, cancellation and modification of a CPAC | Nokia, Nokia Shanghai Bell |
| R3-213384 | (TP to CPAC BL CR to 36.423, LTE_NR_DC_enh2-Core) Max number of PSCells, cancellation and modification of a CPAC | Nokia, Nokia Shanghai Bell |
| R3-213565 | (TP to 37.340 CPAC BL CR) Support of inter-SN CPC | Huawei, CATT, Lenovo, Motorola Mobility |
| R3-213566 | (TP to 38.423/36.423 CPAC BL CR) Support of Early data forwarding | Huawei |
| R3-213567 | (TP to 38.473 38.463 38.401 CPAC BL CRs) CPAC in disaggregated architecture | Huawei |
| R3-213649 | Open issues on conditional PScell Change/Addition | LG Electronics |
| R3-213718 | Remaining issues on CPAC | Lenovo, Motorola Mobility |
| R3-213870 | (TP for CPAC BL CR to TS 38.423) Support of SN-initiated CPC | Ericsson |
| R3-213871 | (TP for CPAC BL CR to TS 38.423) CPC/CPA Cancellation | Ericsson |
| R3-213942 | Remaining issues of Conditional PSCell Change/Addition | CATT |
| R3-213992 | (TP to CPAC BLCR to 36.423) RRC Container content in Conditional PSCell Addition Information Acknowledge | Google Inc. |
| R3-213996 | (TP to CPAC BLCR to 38.423) RRC Container content in Conditional PSCell Addition Information Acknowledge | Google Inc. |
| R3-214127 | (TP for CPAC BL CR to TS 38.423) CPAC Cancellation | Samsung |
| R3-214128 | (TP for CPAC BL CR to TS 36.423) CPAC Cancellation | Samsung |
| R3-214182 | CB: # MRDC3_CPAC - Summary of email discussion | Huawei - moderator |
| R3-214304 | CB: # MRDC3_CPAC - Summary of email discussion | Huawei - moderator |
| R3-214386 | (TP to 36.423 CPAC BL CR) Support of Early data forwarding | Huawei |
| R3-214387 | (TP to 38.473 38.463 38.401 CPAC BL CRs) CPAC in disaggregated architecture | Huawei |
| R3-214388 | (TP to 37.340 CPAC BL CR) Fix the identified error of the BL CR | Huawei |
| R3-214400 | (TP for CPAC BLCR to TS38.423) Data forwarding for MR-DC with 5GC | ZTE |
| R3-214401 | (TP for CPAC BL CR to TS38.423) Enhance Early Status Transfer message for CPA | ZTE |
| 15.1 | General | |
| R3-213492 | Updated Workplan for Rel-17 NR QoE | China Unicom, Ericsson |
| R3-214194 | CB: # QoE1_Workplan - Summary of email discussion | China Unicom - moderator |
| R3-214440 | CB: # QoE1_Workplan - Summary of email discussion | China Unicom - moderator |
| R3-214458 | LS on RAN3 agreements for NR QoE | China Unicom |
| R3-214477 | LS on RAN3 agreements for NR QoE | China Unicom |
| R3-214478 | BLCR to 38.300 | China Unicom |
| R3-214479 | BLCR to 38.300 | China Unicom, Ericsson, ZTE |
| 15.2.1.1 | Configuration, Activation and Deactivation Procedures | |
| R3-213493 | 38300 running CR for NR QoE_ | China Unicom, Huawei, China Southern Power Grid |
| R3-213681 | Discussion on stage 2 description for NR QMC | Nokia, Nokia Shanghai Bell |
| R3-213682 | Introduction of QoE Measurement Collection for NR | Nokia, Nokia Shanghai Bell |
| R3-213944 | Discussion on NR QoE configuration procedures | CATT |
| R3-213945 | Introduction of NR QoE measurements on Xn interface | CATT |
| R3-214040 | Further consideration on NR QoE (de)activation procedure | ZTE, China Telecom, China Unicom |
| R3-214041 | (TP for TS 38.300) Introduce NR QoE | ZTE, China Telecom |
| R3-214070 | Further discussions on configuration and reporting of QoE measurements | Huawei |
| R3-214195 | CB: # QoE2_ Stage2 - Summary of email discussion | ZTE - moderator |
| R3-214247 | (TP to 38.300) Introduction of NR QoE | ZTE |
| R3-214417 | LS on the support for MBS and XR in NR QMC | ZTE |
| R3-214418 | (TP to 38.300) Introduction of NR QoE | ZTE, China Unicom, Nokia, Samsung, Qualcomm, CMCC, CATT, Ericsson, Huawei |
| R3-214423 | CB: # QoE2_ Stage2 - Summary of email discussion | ZTE - moderator |
| R3-214455 | (TP to 38.300) Introduction of NR QoE | ZTE, China Unicom, Nokia, Samsung, Qualcomm, CMCC, CATT, Ericsson, Huawei |
| 15.2.1.2 | Configuration Details | |
| R3-213317 | QoE Configuration and Reporting | Ericsson |
| R3-213318 | CR TS 38.413 QoE Configuration and Reporting - Signalling Design | Ericsson |
| R3-213489 | QoE Configuration and Reporting | China Unicom, China Southern Power Grid |
| R3-213654 | QoE configuration and reporting | Qualcomm Incorporated |
| R3-213683 | Choices for configuration of NR QoE measurements | Nokia, Nokia Shanghai Bell |
| R3-213946 | Discussion on NR QoE configuration details | CATT |
| R3-213964 | Further discussion on QoE Measurement Collection in NR | Samsung |
| R3-213965 | (CR for TS 38.413) Support of NR QoE | Samsung |
| R3-213966 | (CR for TS38.423) Support of NR QoE | Samsung |
| R3-214042 | (TP for TS 38.413) NR QOE configuration | ZTE, China Telecom |
| R3-214043 | (TP for TS 38.423) NR QOE configuration | ZTE, China Telecom |
| R3-214044 | Discussion on NR QOE configuration | ZTE, China Telecom, China Unicom |
| R3-214071 | CR to 38.413 on Introduction of QoE measurement | Huawei, China Mobile, China Unicom |
| R3-214072 | Further discussions on overland handling | Huawei |
| R3-214073 | Further discussions on per-slice QoE measurement | Huawei |
| R3-214110 | Further discussions on per-slice QoE measurement | CMCC |
| R3-214196 | CB: # QoE3_Configuration_Report - Summary of email discussion | Huawei - moderator |
| R3-214380 | CR to 38.413 on Introduction of QoE measurement | Huawei, China Mobile, China Unicom |
| 15.2.2 | Measurement Collection and Continuity in Intra-System Intra-RAT Mobility | |
| R3-213316 | CR TS 38.423 Mobility Support for NR QoE Measurement Collection | Ericsson |
| R3-213319 | QoE Mobility Support | Ericsson |
| R3-213490 | QoE measurement in mobility scenarios | China Unicom, China Southern Power Grid |
| R3-213655 | QoE measurement collection and reporting continuity in mobility scenarios | Qualcomm Incorporated |
| R3-213684 | Open issues on mobility | Nokia, Nokia Shanghai Bell |
| R3-213791 | Discussion on Measurement Collection and Continuity in Intra-System Intra-RAT Mobility | ZTE |
| R3-213947 | Discussion on Measurement Collection and Continuity in Intra-System Intra-RAT Mobility | CATT |
| R3-214045 | Discussion on Measurement Collection and Continuity in Intra-System Intra-RAT Mobility | ZTE, China Telecom, China Unicom |
| R3-214074 | Further discussions on measurement Collection and Continuity in Intra-System Intra-RAT Mobility | Huawei |
| R3-214131 | On the reception of QoE configuration in a non-supporting node | China Telecom Corporation Ltd. |
| R3-214197 | CB: # QoE4_Mobility - Summary of email discussion | Nokia - moderator |
| 15.3 | Support for RAN-Visible QoE | |
| R3-213320 | RAN-visible QoE Metrics | Ericsson |
| R3-213321 | RAN-visible QoE Configuration and Reporting | Ericsson |
| R3-213491 | RAN visible QoE configuration and reporting | China Unicom, China Southern Power Grid |
| R3-213656 | Support for RAN Visible QoE | Qualcomm Incorporated |
| R3-213685 | Analysis of metrics for RAN visible QoE | Nokia, Nokia Shanghai Bell |
| R3-213948 | Discussion on RAN visible QoE configuration and reporting | CATT |
| R3-213949 | [Draft]LS on the configuration and report of the RAN-visible QoE | CATT |
| R3-213967 | Discussion on RAN visible QoE | Samsung |
| R3-213968 | (CR for TS38.473) Support of QoE information transfer | Samsung |
| R3-214046 | Further consideration on RAN visible QoE | ZTE, China Telecom |
| R3-214047 | [draft] LS on RAN visible QoE | ZTE, China Telecom |
| R3-214075 | Further discussions on RAN-visible QoE | Huawei |
| R3-214076 | Draft LS on RAN-visible QoE conclusions | Huawei |
| R3-214109 | Further discussions on RAN visible QoE | CMCC |
| R3-214198 | CB: # QoE5_RANVisible - Summary of email discussion | Ericsson - moderator |
| 15.4 | Alignment of Radio-Related Measurement and QoE Measurements | |
| R3-213322 | The Alignment of Radio-Related Measurements and QoE Measurements | Ericsson |
| R3-213657 | Alignment of Radio-Related Measurement and QoE Measurements | Qualcomm Incorporated |
| R3-213686 | Remaining open issues for alignment of radio-related measurements and QoE measurements | Nokia, Nokia Shanghai Bell |
| R3-213950 | Discussion on Alignment of MDT and QoE Measurements | CATT |
| R3-213969 | Discussion on the alignment of Radio-Related Measurement and QoE Measurement | Samsung |
| R3-214048 | Discussion on alignment of MDT and QoE Measurements | ZTE, China Telecom, China Unicom |
| R3-214049 | (TP for 38.401) Alignment of MDT and QoE Measurements | ZTE, China Telecom, China Unicom |
| R3-214050 | (TP for E1/F1) Alignment of MDT and QoE Measurements | ZTE, China Telecom |
| R3-214077 | Further discussions on Radio-Related Measurement and QoE Measurements | Huawei |
| R3-214108 | Further discussions on alignment of radio related measurement and QoE measurement | CMCC |
| R3-214199 | CB: # QoE6_MDTAlignment - Summary of email discussion | Qualcomm - moderator |
| R3-214454 | CB: # QoE6_MDTAlignment - Summary of email discussion | Qualcomm - moderator |
| 16.1 | General | |
| R3-213169 | Introduction of support for eNPN | Qualcomm Incorporated |
| R3-213170 | Supporting enhanced private network | Huawei |
| R3-213177 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-213301 | Work Plan for Enhancement for Private Network Support for NG-RAN WI | China Telecommunication |
| R3-214183 | CB: # NPN1_Workplan_BLCRs - Summary of email discussion | China Telecom - moderator |
| R3-214502 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-214503 | Introduction of support for eNPN | Qualcomm Incorporated |
| R3-214504 | Supporting enhanced private network | Huawei |
| 16.2.1 | Cell Access Control | |
| R3-213266 | (TP for BL CR for 38.413) Open issues for onboarding signalling | Qualcomm Incorporated |
| R3-213302 | On configuration of necessary parameters for cell access of external credential user | China Telecommunication |
| R3-213303 | TP for eNPN BL CR for 38.413 | China Telecommunication |
| R3-213331 | Discussion on cell access control for eNPN | CATT |
| R3-213455 | (TP for TS 38.300) Support for onboarding stage 2 | Nokia, Nokia Shanghai Bell |
| R3-213456 | (TP for TS 38.413) Support for Onboarding stage 3 | Nokia, Nokia Shanghai Bell |
| R3-213586 | Cell access control for UE onboarding | Ericsson |
| R3-213587 | Cell access control for SNPN access using external credentials | Ericsson |
| R3-213642 | (TP for ePRN BLCR for TS 38.413) Supporting enhanced private network | Huawei |
| R3-213643 | Supporting enhanced private network | Huawei |
| R3-213763 | Dicussion on On-Demand PRS | ZTE Corporation |
| R3-213766 | (TP for TS 38.413)Introduce eNPN | ZTE Corporation |
| R3-213767 | (TP for TS 38.300)Introduce eNPN | ZTE Corporation |
| R3-214028 | Support of access using credentials from credentials holder | LG Electronics |
| R3-214029 | (TP for eNPN BL CR for TS 38.413) Support of access using credentials from credentials holder | LG Electronics |
| R3-214184 | CB: # NPN2_CellAccessControl - Summary of email discussion | Nokia - moderator |
| R3-214283 | (TP for TS 38.300) Support for onboarding stage 2 | Nokia, Nokia Shanghai Bell |
| R3-214285 | (TP for ePRN BLCR for TS 38.413) Supporting enhanced private network | Huawei |
| R3-214292 | (TP for BL CR for 38.410) Terminology change | Qualcomm |
| R3-214299 | (TP for TS 38.300) Support for onboarding stage 2 | Nokia, Nokia Shanghai Bell |
| 18.1 | General | |
| R3-214115 | Work plan for FS_NR_ENDC_data_collect | CMCC |
| R3-214129 | TR 37.817 v0.2.0 | China Mobile Com. Corporation |
| R3-214219 | CB: # AIRAN1_Workplan - Summary of email discussion | CMCC - moderator |
| R3-214517 | TR 37.817 v0.2.0 | China Mobile Com. Corporation |
| 18.2 | High-Level Principles and Definitions | |
| R3-213196 | AI/ML Model Performance and Reliability Evaluation | Futurewei |
| R3-213211 | Discussion on AI/ML-based functional framework for RAN intelligence | Deutsche Telekom AG |
| R3-213294 | Proposed TP to TR 37.817 on high-level principles and functional framework | NEC |
| R3-213373 | AI/ML Architecture | Qualcomm Incorporated, Deutsche Telekom |
| R3-213418 | (TP for SON BL CR for TS 37.817): Framework for RAN intelligence | Ericsson |
| R3-213468 | High level principle and Functional Framework of AI/ML enabled NG-RAN Network | Intel Corporation |
| R3-213540 | Discussion on framework of AI | CATT |
| R3-213712 | Discussion on Functional Framework and High-Level Principles | Samsung |
| R3-213723 | Remaining issues on AI functional framework | Lenovo, Motorola Mobility |
| R3-213756 | Left issue on AI Functional Framework for RAN Intelligence | ZTE Corporation, China Unicom |
| R3-213892 | (TP for TR 37.817): Further discussions on the AI/ML Framework | Nokia, Nokia Shanghai Bell |
| R3-214078 | Further discussions on general principles and frame work | Huawei |
| R3-214220 | CB: # AIRAN2_GeneralandFramework - Summary of email discussion | Lenovo - moderato |
| R3-214344 | TP for AI RAN general framework | lenovo |
| R3-214427 | TP for AI RAN general framework | lenovo |
| R3-214446 | LS to SA5 on model deployment and update from OAM to NG-RAN | Lenovo |
| R3-214480 | TP for AI RAN general framework | lenovo |
| R3-214481 | LS to SA5 on model deployment and update from OAM to NG-RAN | Lenovo |
| 18.3 | Use Cases for Artificial Intelligence in RAN and Potential Benefits | |
| R3-213956 | Solution to AI based ES in RAN Split Architecture | China Telecom Corporation Ltd. |
| 18.4.1 | Network Energy Saving | |
| R3-213295 | Proposed TP to TR 37.817 on Energy Saving solutions and standard impacts | NEC |
| R3-213469 | AI/ML based network energy saving | Intel Corporation |
| R3-213713 | Discussion on Standard Impact for RAN Intelligence (Network Energy Saving) | Samsung |
| R3-213757 | Solution to AI based Energy Saving | ZTE Corporation, Lenovo, Motorola Mobility, China Unicom |
| R3-213779 | Network Energy Saving | Ericsson |
| R3-213888 | AI/ML-based Energy Saving – Solutions and Standard Impacts | Futurewei |
| R3-213894 | (TP for TR 37.817): Standards Impacts for the AI/ML Energy Saving Use Case | Nokia, Nokia Shanghai Bell |
| R3-214054 | Solution to AI based ES in RAN Split Architecture | China Telecom Corporation Ltd. |
| R3-214079 | Further discussions on spec impacts of energy saving | Huawei |
| R3-214114 | (TP to TR 37.817) Solutions for AI based Energy Saving | CMCC |
| R3-214221 | CB: # AIRAN3_ESSolution - Summary of email discussion | Intel - moderator |
| R3-214415 | TP to 37.817 on AI/ML based network energy saving | Intel |
| R3-214459 | TP to 37.817 on AI/ML based network energy saving | Intel |
| R3-214473 | TP to 37.817 on AI/ML based network energy saving | Intel |
| R3-214482 | TP to 37.817 on AI/ML based network energy saving | Intel |
| 18.4.2 | Load Balancing | |
| R3-213296 | Proposed TP to TR 37.817 on Load Balancing solutions and standard impacts | NEC |
| R3-213420 | AI/ML Load Balancing use case | Ericsson |
| R3-213470 | AI/ML based load balancing | Intel Corporation |
| R3-213541 | Discussion on I/O for load prediction | CATT |
| R3-213714 | Discussion on Standard Impact for RAN Intelligence (Load Balancing) | Samsung |
| R3-213725 | Discussion on traffic load prediction | Lenovo, Motorola Mobility |
| R3-213758 | Solution to AI based load prediction | ZTE Corporation, China Unicom |
| R3-213893 | (TP for TR 37.817): Standards Impacts for the AI/ML Load Balancing Use Case | Nokia, Nokia Shanghai Bell |
| R3-214080 | Further discussions on spec impacts of load balancing & traffic steering | Huawei |
| R3-214124 | (TP to TR 37.817) Solutions for AI-based load balancing | CMCC |
| R3-214222 | CB: # AIRAN4_LBSolution - Summary of email discussion | Nokia - moderator |
| R3-214408 | (TP for TR 37.817) AI/ML Load Balancing Solution | Nokia, Nokia Shanghai Bell |
| R3-214460 | (TP for TR 37.817) AI/ML Load Balancing Solution | Nokia, Nokia Shanghai Bell |
| R3-214483 | (TP for TR 37.817) AI/ML Load Balancing Solution | Nokia, Nokia Shanghai Bell |
| 18.4.3 | Mobility Optimization | |
| R3-213297 | Proposed TP to TR 37.817 on Mobility Optimization solutions and standard impacts | NEC |
| R3-213471 | AI/ML based mobility optimization | Intel Corporation |
| R3-213542 | On where to deploy the UE location prediction entity | CATT |
| R3-213543 | Discussion on I/O for UE location prediction | CATT |
| R3-213648 | Support of AI/ML enabled Mobility Optimization for NG-RAN and EN-DC | LG Electronics |
| R3-213715 | Discussion on Standard Impact for RAN Intelligence (Mobility Optimization) | Samsung |
| R3-213724 | Discussion on standard impact to support mobility optimization | Lenovo, Motorola Mobility |
| R3-213759 | Solution to AI based UE Trajectory Prediction | ZTE Corporation, China Unicom, CMCC |
| R3-213780 | AI/ML based mobility optimization: Mobility performance feedback after HO | Ericsson |
| R3-213787 | Standardization impacts of Mobility Optimization Use Case for AI | InterDigital |
| R3-213895 | Standards Impacts for the AI/ML Mobility Use Case | Nokia, Nokia Shanghai Bell |
| R3-214081 | Further discussions on spec impacts of moblity enhancements | Huawei |
| R3-214113 | (TP to TR 37.817) Solutions for AI-based mobility optimization | CMCC |
| R3-214130 | Discussion on AI based mobility optimization | vivo |
| R3-214223 | CB: # AIRAN5_MoblitySolution - Summary of email discussion | CMCC - moderator |
| R3-214411 | TP to TR37.817 on AI-based mobility solution | CMCC |
| R3-214461 | TP to TR37.817 on AI-based mobility solution | CMCC |
| R3-214484 | TP to TR37.817 on AI-based mobility solution | CMCC |
| 18.5 | Others | |
| R3-213760 | Analysis on data transmission for RAN AI | ZTE Corporation, China Unicom |
| R3-214224 | CB: # AIRAN6_DataSecandTrans - Summary of email discussion | ZTE - moderator |
| R3-214351 | Analysis on data transmission for RAN AI | ZTE Corporation, China Unicom |
| 19.1 | General | |
| R3-213164 | Introduction of NR Positioning enhancements to NRPPa | Ericsson |
| R3-213842 | Overview and Discussion of the received positioning liaisons | Ericsson |
| R3-214516 | Introduction of NR Positioning enhancements to NRPPa | Ericsson |
| 19.2.1 | Positioning Accuracy Improvements | |
| R3-213107 | LS on support of UL-AOA/ZOA assistance information signalling for NR positioning | RAN1, Intel Corporation |
| R3-213445 | (TP for NR_pos_enh BL CR for TS 38.455) UL-AOA/ZOA assistance information | Nokia, Nokia Shanghai Bell |
| R3-213613 | Discussion on support of UL-AOA/ZOA assistance information signalling for NR positioning | Huawei |
| R3-213614 | (TP for POS BL CR for TS 38.455): Support of UL-AOA/ZOA assistance information signalling for NR positioning | Huawei |
| R3-213615 | Support of UL-AOA/ZOA assistance information signalling for NR positioning | Huawei |
| R3-213616 | [Draft] reply LS on support of UL-AOAZOA assistance information signalling for NR positioning | Huawei |
| R3-213617 | Introduction of NR Positioning enhancements to F1AP | Huawei |
| R3-213618 | (TP for POS BL CR for TS 38.455): Positioning enhancement | Huawei |
| R3-213619 | Positioning enhancement | Huawei |
| R3-213674 | CR for 38.473 on Positioning Accuracy Improvements | CATT |
| R3-213761 | Dicussion on the Positioning Accuracy Improvements | ZTE Corporation |
| R3-213762 | TP for TS38.455 on Positioning Accuracy Imporvements | ZTE Corporation |
| R3-213851 | Discussion on Rel-17 UL AoA enhancements with TP to NRPPa BL CR | Ericsson |
| R3-213852 | TP to F1AP BL CR for Rel-17 UL AoA enhancements | Ericsson |
| R3-214200 | CB: # 1901_Pos_AccEnhs_AoA-AoZ_LS - Summary of email discussion | Ericsson - moderator |
| R3-214287 | Discussion on Rel-17 UL AoA enhancements with TP to NRPPa BL CR | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, CATT, ZTE |
| R3-214296 | Introduction of NR Positioning enhancements to F1AP | Huawei |
| R3-214297 | Discussion on Rel-17 UL AoA enhancements with TP to NRPPa BL CR | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, CATT, ZTE |
| R3-214309 | CB: # 1901_Pos_AccEnhs_AoA-AoZ_LS - Summary of email discussion | Ericsson - moderator |
| R3-214439 | Introduction of NR Positioning enhancements to F1AP | Huawei |
| 19.2.2 | RRC_INACTIVE State Positioning | |
| R3-213620 | (TP for POS BL CR for TS 38.455): Discussion on RRC inactive positioning | Huawei |
| R3-213675 | Positioning for UEs in RRC_INACTIVE state | CATT |
| R3-213853 | Discussion on support of RRC-Inactive Positioning | Ericsson |
| R3-213970 | Positioning in RRC inactive state | Samsung |
| R3-214201 | CB: # 1902_Pos_RRC_INACTIVE - Summary of email discussion | Huawei - moderator |
| 19.2.3 | On-Demand PRS Transmission and Reception | |
| R3-213119 | LS on On-demand PRS | RAN2 |
| R3-213446 | (TP for NR_pos_enh BL CR for TS 38.455) Pre-defined PRS configurations for on-demand PRS | Nokia, Nokia Shanghai Bell |
| R3-213612 | [Draft] reply LS on on-demand PRS | Huawei |
| R3-213621 | (TP for POS BL CR for TS 38.455, TS 38.473): On-demand PRS | Huawei |
| R3-213673 | Support of UL-AOAZOA Assistance Information Signalling | CATT |
| R3-213676 | Further Consideration on On-Demand PRS Procedure | CATT |
| R3-213764 | TP for TS38.455 on On-Demand PRS | ZTE Corporation |
| R3-213854 | TP to NRPPa BL CR: Addition of On-demand DL-PRS information | Ericsson |
| R3-213855 | TP to F1AP BL CR: Addition of On-demand DL-PRS information | Ericsson |
| R3-214202 | CB: # 1903_Pos_OnDemandPRS - Summary of email discussion | Nokia - moderator |
| R3-214286 | (TP for NR_pos_enh BL CR for TS 38.455) Pre-defined PRS configurations for on-demand PRS | Nokia, Nokia Shanghai Bell |
| 19.3 | Support for Latency Improvement | |
| R3-213398 | Scheduling Location in Advance to Reduce Latency | Qualcomm Incorporated |
| R3-213622 | (TP for POS BL CR for TS 38.455, TS 38.473): Latency improvement in positioning | Huawei |
| R3-213677 | Further Consideration on Positioning Latency Improvement | CATT |
| R3-213856 | Discussion on latency improvements for Rel-17 positioning | Ericsson |
| R3-213971 | Positioning latency improvement | Samsung |
| R3-214203 | CB: # 1904_Pos_LatencyImprovement - Summary of email discussion | Qualcomm - moderator |
| R3-214300 | (TP for POS BL CR for TS 38.455): Latency improvement in positioning | Huawei |
| R3-214301 | (TP for POS BL CR for TS 38.473): Latency improvement in positioning | Huawei |
| R3-214310 | CB: # 1904_Pos_LatencyImprovement - Summary of email discussion | Qualcomm - moderator |
| R3-214486 | BL CR to 38.473 | Huawei |
| 20.1 | General | |
| R3-213152 | Clarification of NAS Node Selection Function for NTN nodes providing access over multiple countries | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei |
| R3-213153 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-213154 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-213183 | Support Non-Terrestrial Networks | Huawei, Thales, Ericsson, ZTE, Qualcomm Incorporated |
| R3-213195 | NTN ephemeris format and usage | THALES, Ericsson |
| R3-213346 | (TP for BL CR TS 38.300) NTN Stage 2 Update | Huawei |
| R3-213786 | Considerations on the Current Status of NTN in Rel-17 | Ericsson LM |
| R3-214204 | CB: # 2001_NTN_General - Summary of email discussion | Thales - moderator |
| R3-214352 | (TP for BL CR TS 38.300) NTN Stage 2 Update | Huawei |
| R3-214514 | Support Non-Terrestrial Networks | Huawei, Thales, Ericsson, ZTE, Qualcomm Incorporated |
| R3-214515 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| 20.2.1 | Network Identifier Handling | |
| R3-213310 | Discussion on Network Identifier Handling | China Telecommunication |
| R3-213343 | Cell Identifier management | Huawei |
| R3-213396 | (TP for BL CR for 38.300) Cell ID handling in stage 2 | Qualcomm Incorporated |
| R3-213397 | (TP for BL CR for 38.413) Verification of ULI | Qualcomm Incorporated |
| R3-213536 | (TP for BL CR for TS 38.300) Cell ID handling on NG/Xn interface | Nokia, Nokia Shanghai Bell |
| R3-213588 | On usage of cell identifiers for NTN | Ericsson |
| R3-213589 | [TP for BL CR 38.300] On Cell Identifiers for NR NTN | Ericsson |
| R3-213669 | Discussion on CGI handling in RAN | CATT |
| R3-214013 | Cell ID Handling in Handover | Samsung |
| R3-214100 | Discussion on Network Identifier Handling | CMCC |
| R3-214205 | CB: # 2002_NTN_NW-ID - Summary of email discussion | Ericsson - moderator |
| R3-214353 | TP for the BL CR to TS38.300 | Ericsson |
| 20.2.2 | Registration Update and Paging Handling | |
| R3-213342 | TAC in ULI | Huawei |
| R3-213537 | (TP for BL CR for TS 38.300) Discussion on TAI used in Registration Update and Paging Handling | Nokia, Nokia Shanghai Bell |
| R3-214206 | CB: # 2003_NTN_Reg_Pag - Summary of email discussion | Nokia - moderator |
| R3-214341 | (TP for BL CR for TS 38.300) add the correspondence for TAI and geographical area | Nokia, Nokia Shanghai Bell |
| R3-214354 | (TP for BL CR for TS 38.300) add the correspondence for TAI and geographical area | Nokia, Nokia Shanghai Bell |
| 20.2.3 | Cell Relation Handling | |
| R3-213341 | Time Window management for signalling reduction | Huawei |
| R3-213670 | On remaining issues regarding cell relation handling | CATT |
| R3-214085 | Further Discussion on Cell Relations for NTN | ZTE |
| R3-214099 | Discussion on cell relation | CMCC |
| R3-214207 | CB: # 2004_NTN_Cell_Rel - Summary of email discussion | CMCC - moderator |
| 20.2.4 | Feeder Link Switch-Over for LEO | |
| R3-213311 | Further discussion on Feeder Link Switchover | China Telecommunication |
| R3-213538 | (TP for BL CR for TS 38.300) Discussion on feeder link switchover | Nokia, Nokia Shanghai Bell |
| R3-214086 | Further Discussion on Feeder Link Switch-over for LEO | ZTE |
| R3-214208 | CB: # 2005_NTN_Feeder_Link - Summary of email discussion | ZTE - moderator |
| R3-214342 | (TP for BL CR for TS 38.300) Discussion on feeder link switchover | Nokia, Nokia Shanghai Bell |
| R3-214363 | CB: # 2005_NTN_Feeder_Link - Summary of email discussion | ZTE - moderator |
| 20.2.5 | Aspects Related to Country-Specific Routing | |
| R3-213344 | Country-specific routing issues | Huawei |
| R3-213539 | (TP for BL CR for TS 38.413) Country Specific Routing for an RRC CONNECTED UE | Nokia, Nokia Shanghai Bell |
| R3-213671 | Discussion on country-specific CN selection | CATT |
| R3-214087 | Discussion on Country-specific Routing for NTN | ZTE |
| R3-214209 | CB: # 2006_NTN_Country_Routing - Summary of email discussion | CATT - moderator |
| R3-214364 | CB: # 2006_NTN_Country_Routing - Summary of email discussion | CATT - moderator |
| 20.2.6 | Others | |
| R3-213345 | NTN-NTN and NTN-TN mobility | Huawei |
| R3-214210 | CB: # 2007_NTN_Others - Summary of email discussion | Huawei - moderator |
| R3-214365 | CB: # 2007_NTN_Others - Summary of email discussion | Huawei - moderator |
| 21.1 | General | |
| R3-213172 | Introduction of Enhanced IIoT support over NG | CATT, Nokia, Nokia Shanghai Bell, Samsung, Huawei, Ericsson, ZTE |
| R3-213173 | Introduction of Enhanced IIoT support over Xn | Ericsson, Samsung, Huawei, ZTE,CATT, Nokia, Nokia Shanghai Bell |
| R3-213174 | Introduction of Enhanced IIoT support over E1 | ZTE, Nokia, Nokia Shanghai Bell, Samsung, CATT, Huawei, Ericsson |
| R3-213175 | Introduction of Enhanced IIoT support over F1 | Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE, Samsung |
| R3-213774 | [TP for BL CR for TS 38.423]: Correction to the Baseline CR | Ericsson |
| R3-214185 | CB: # NRIIOT1_BLCRs - Summary of email discussion | Nokia - moderator |
| R3-214508 | Introduction of Enhanced IIoT support over Xn | Ericsson, Samsung, Huawei, ZTE,CATT, Nokia, Nokia Shanghai Bell |
| 21.2 | Support for Propagation Delay Compensation Enhancements | |
| R3-213241 | Further discussion on Propagation Delay Compensation enhancements | ZTE |
| R3-213377 | Discussion on Further enhanced NR-IIoT: Enhancements for support of time synchronization | Ericsson |
| R3-213378 | Enhancements for support of time synchronization | Ericsson |
| R3-213379 | Enhancements for support of time synchronization | Ericsson |
| R3-213449 | Impact of handover on time synchronization | Nokia, Nokia Shanghai Bell |
| R3-213645 | (TP for eIIoT BLCR for 38.423) Propagation delay compensation and timing accuracy during handover | Huawei |
| R3-213646 | (TP for eIIoT BLCR for 38.413) Propagation delay compensation and timing accuracy during handover | Huawei |
| R3-213907 | Discussion on supporting the time synchronization error budget | Samsung |
| R3-213951 | Discussion on Propagation Delay Compensation Enhancements | CATT |
| R3-214186 | CB: # NRIIOT2_PDC - Summary of email discussion | ZTE - moderator |
| 21.3 | Enhancements Based on New QoS Related Parameters | |
| R3-213242 | (TP for Introduction of Enhanced IIoT support) Analysis of New QoS Related parameters | ZTE |
| R3-213243 | (TP for Introduction of the enhanced IIoT over E1) New QoS related parameters | ZTE |
| R3-213447 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.413) Resolution of TSCAI open issues | Nokia, Nokia Shanghai Bell |
| R3-213448 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.423) Impact of handover on Survival Time | Nokia, Nokia Shanghai Bell |
| R3-213647 | (TP for eIIoT BLCR for 38.473) Survival time remaining issues | Huawei |
| R3-213910 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.413) Discussion on the remaining issues for the Survival Time | Samsung |
| R3-213913 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.423) The maximum value for the Survival Time | Samsung |
| R3-213952 | Discussion on new QoS related parameters | CATT |
| R3-213953 | (TP for [NR_IIOT_URLLC_enh-Core] BLCR for TS 38413) new QoS related parameters | CATT |
| R3-214187 | CB: # NRIIOT3_NewQoS - Summary of email discussion | Huawei - moderator |
| 22.1 | General | |
| R3-213138 | Introduction of MBS(BL CR for 38.463) | CATT |
| R3-213139 | Introduction of NR MBS | Lenovo, Motorola mobility |
| R3-213144 | MBS BL CR for TS38.410 | ZTE |
| R3-213145 | Introduction of NR MBS | Huawei, CMCC |
| R3-213147 | Introduction of NR MBS | Samsung |
| R3-213148 | BL CR for NR MBS for 38.413 | Qualcomm |
| R3-213150 | Introduction of NR MBS | LG Electronics |
| R3-213151 | Introduction of NR Multicast and Broadcast Services | Ericsson |
| R3-213179 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-214211 | CB: # MBS1_BLCRs - Summary of email discussion | LG Electronics - moderator |
| R3-214509 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-214510 | Introduction of NR MBS | Huawei, CMCC |
| R3-214511 | MBS BL CR for TS38.410 | ZTE |
| R3-214512 | BL CR for NR MBS for 38.413 | Qualcomm |
| R3-214513 | Introduction of NR Multicast and Broadcast Services | Ericsson |
| R3-214518 | BL CR to TS38.420 | CMCC |
| 22.2.2 | Session Management over NG | |
| R3-213457 | (TP for 38.300& 38.410) Stage 2 for Multicast and Broadcast | Nokia, Nokia Shanghai Bell |
| R3-213458 | (TP for 38.413) Stage 3 for MBS Group Paging | Nokia, Nokia Shanghai Bell |
| R3-213459 | (TP for 38.413) Stage 3 for MBS Context and UE MBS Context | Nokia, Nokai Shanghai Bell |
| R3-213460 | (TP for 38.413) Stage 3 for User Plane Shared Delivery Tunnel | Nokia, Nokia Shanghai Bell |
| R3-213547 | TP for 38.413 on session management for broadcast | CATT,CBN,Huawei |
| R3-213548 | Discussion on MBS session management for multicast | CATT,CBN |
| R3-213555 | Consideration on Multicast Session Management | Huawei, CBN, China Unicom, Lenovo, Motorola Mobility, Qualcomm Incorporated, China Telecom |
| R3-213556 | (TP to TS 38.410 BL CR) Multicast Session Management | Huawei, CBN, China Unicom, Lenovo, Motorola Mobility, Qualcomm Incorporated, China Telecom |
| R3-213557 | (TP to TS 38.413 BL CR) Multicast Session Management | Huawei, CMCC, Lenovo, Motorola Mobility, Qualcomm Incorporated |
| R3-213590 | [TP for BL CR 38.300] Orderly specification work for NR MBS Session Management | Ericsson |
| R3-213591 | [TP for BL CR 38.413 and 38.423] Orderly specification work for NR MBS Session Management | Ericsson |
| R3-213651 | Group Paging for MBS Multicast | Qualcomm Incorporated |
| R3-213743 | Discussion on Group paging for Multicast Session Activation Notification | Lenovo, Motorola Mobility |
| R3-213744 | (TP to TS 38.420 BL CR) Group paging for Multicast Session Activation Notification | Lenovo, Motorola Mobility, Huawei |
| R3-213745 | (TP to TS 38.423 BL CR) Group paging for Multicast Session Activation Notification | Lenovo, Motorola Mobility, Huawei |
| R3-213768 | Discussion on multicast MBS group paging | LG Electronics |
| R3-213769 | (TP for NR_MBS BL CR for TS 38.413) Discussion on multicast MBS group paging | LG Electronics |
| R3-213788 | (TP for TS 38.413) Management of multicast session | ZTE |
| R3-213789 | (TP for TS 38.410) Management of multicast session | ZTE |
| R3-213989 | (TP to TS 38.415 BL CR) Support of NR MBS data transmission | Huawei, CBN, China Telecom |
| R3-214119 | MBS Session management over NG for multicast | CMCC |
| R3-214120 | (TP to TS 38.410 ) MBS session management over NG | CMCC |
| R3-214121 | (TP to TS 38.300 ) MBS session management over NG | CMCC, Huawei |
| R3-214212 | CB: # MBS2_SessMgmt - Summary of email discussion | Ericsson - moderator |
| R3-214291 | (TP for 38.413) Stage 3 for MBS Group Paging | Nokia, Nokia Shanghai Bell |
| R3-214305 | CB: # MBS2_SessMgmt - Summary of email discussion | Ericsson - moderator |
| R3-214378 | (TP to TS 38.420 BL CR) Group paging for Multicast Session Activation Notification | Lenovo, Motorola Mobility, Huawei, Nokia, Nokia Shanghai Bell, CMCC |
| R3-214379 | (TP to TS 38.423 BL CR) Group paging for Multicast Session Activation Notification | Lenovo, Motorola Mobility, Huawei, Nokia, Nokia Shanghai Bell, CMCC |
| R3-214381 | (TP to TS 38.410 BL CR) Multicast Group Paging | Huawei, CBN, China Unicom, Lenovo, Motorola Mobility, Qualcomm Incorporated, China Telecom, Nokia, Nokia Shanghai Bell, CMCC |
| R3-214430 | (TP for 38.413) Stage 3 for MBS Group Paging | Nokia, Nokia Shanghai Bell, Huawei |
| 22.2.3 | Dynamic Change Between PTP and PTM for UEs in RRC_CONNECTED State | |
| R3-213549 | Discussion on dynamic change between PTM and PTP | CATT |
| R3-213577 | (TP to TS 38.401 BL CR) Support of PTP and PTM switch | Huawei, CBN, China Unicom, China Telecom |
| R3-213706 | F1 tunnel and flow control for MBS | Samsung |
| R3-213771 | Discussion on switching decision between PTP and PTM | LG Electronics |
| R3-213832 | Mode switching for NR MBS | ZTE |
| R3-214094 | Discussion on dynamic change between PTP and PTM | CMCC |
| R3-214213 | CB: # MBS3_PTPMSwitch - Summary of email discussion | Samsung - moderator |
| R3-214306 | CB: # MBS3_PTPMSwitch - Summary of email discussion | Samsung - moderator |
| R3-214385 | (TP to TS 38.401 BL CR) Support of PTP and PTM switch | Huawei, CBN, China Unicom, China Telecom |
| 22.2.4 | Bearer Management over F1/E1 | |
| R3-213544 | Consideration on Flow Control Mechanism over F1-U(TP to BLCR of TS 38.425) | CATT,CBN |
| R3-213545 | Consideration on MBS Session Management at F1E1 interface(TP to TS 38.473 and TS 38.463) | CATT,CBN |
| R3-213578 | (TP to TS 38.401 BL CR) Bearer management over F1 and E1 | Huawei, CBN, China Telecom |
| R3-213579 | (TP to TS 38.425 BL CR) Flow Control for MBS | Huawei, CBN, China Telecom |
| R3-213592 | [TP for BL CR for 38.401] On F1 and E1 protocol aspects for NR MBS | Ericsson |
| R3-213593 | [TP for BL CR for 38.473 and 38.463] On F1 and E1 protocol aspects for NR MBS | Ericsson |
| R3-213652 | (TP to TS 38.470 BL CR) Multicast Session Management | Qualcomm Incorporated, Huawei, Lenovo, Motorola Mobility |
| R3-213653 | (TP to TS 38.473 BL CR) Multicast Session Management | Qualcomm Incorporated, Huawei, Lenovo, Motorola Mobility |
| R3-213707 | TP for TS38.473 BL: Introduction of NR MBS | Samsung |
| R3-213708 | TP for TS38.463 BL: Addition of session management procedure | Samsung |
| R3-213741 | Bearer Management over F1/E1 for Multicast Session | Lenovo, Motorola Mobility |
| R3-213742 | MCCH Configuration and MCCH Contents Delivery over F1 | Lenovo, Motorola Mobility |
| R3-213746 | (TP to TS 38.460 BL CR) Support of Multicast Distribution Setup and Release | Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated |
| R3-213747 | (TP to TS 38.463 BL CR) Support of Multicast Distribution Setup and Release | Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated |
| R3-213770 | (TP for NR_MBS BL CR for TS 38.473) Discussion on multicast MBS group paging | LG Electronics |
| R3-213833 | F1-U tunnel and flow control for NR MBS | ZTE |
| R3-214095 | Discussion on MBS Bearer Management | CMCC |
| R3-214214 | CB: # MBS4_BearerMgmt - Summary of email discussion | Huawei - moderator |
| R3-214307 | CB: # MBS4_BearerMgmt - Summary of email discussion | Huawei - moderator |
| R3-214382 | (TP to TS 38.401 BL CR) Bearer management over F1 and E1 | Huawei, CBN, China Telecom, , Nokia, Nokia Shanghai Bell |
| R3-214383 | (TP to TS 38.470 BL CR) Multicast Group Paging | Qualcomm Incorporated, Huawei, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell |
| R3-214384 | (TP to TS 38.473 BL CR) Multicast Group Paging | Qualcomm Incorporated, Huawei, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell |
| 22.2.5 | Others | |
| R3-213740 | Remaining Issues on MBS Service Area Management | Lenovo, Motorola Mobility |
| R3-214215 | CB: # MBS5_ServiceAreaMgmt - Summary of email discussion | Lenovo - moderato |
| 22.3.1 | Mobility Between MBS Supporting Nodes | |
| R3-213374 | Data forwarding in handover with MBS multicast | Qualcomm Incorporated, Huawei, Samsung, Lenovo, Nokia, Nokia Shanghai Bell, CATT, CMCC, LG Electronics, CBN |
| R3-213461 | (TP for 38.415) Seamless Mobility between two MBS Supporting Nodes and use of data forwarding | Nokia, Nokia Shanghai Bell |
| R3-213462 | (TP for 38.300) MBS Stage 2 for Mobility between MBS supporting nodes | Nokia, Nokia Shanghai Bell |
| R3-213550 | Supporting lossless handover while retaining flexible MRB mapping | CATT |
| R3-213551 | LS on aligning MRB PDCP Count among multiple gNBs | CATT |
| R3-213552 | TP on TS 38.300 on multicast lossless handover | CATT |
| R3-213594 | On mobility between gNBs supporting NR MBS | Ericsson |
| R3-213595 | [TP for BL CR TS 38.401 and 38.463] HO between supporting gNBs | Ericsson |
| R3-213738 | Enhancements to support loss-less handover for NR multicast | Lenovo, Motorola Mobility |
| R3-213834 | NR MBS Lossless handover for inter-gNB scenario | ZTE |
| R3-213835 | Discussion on MBS mobility procedure | ZTE |
| R3-213985 | Way Forward on Mobility between MBS supporting nodes | Huawei, Qualcomm Incorporated, CMCC, Lenovo, Nokia, Nokia Shanghai Bell, CBN, China Telecom, CATT, LG Electronics, Samsung, China Unicom |
| R3-213986 | (TP to TS 38.300 BL CR) Mobility between MBS supporting nodes | Huawei, CBN, China Unicom, China Telecom |
| R3-213987 | (TP to TS38.300 BL CR) Consideration on DL PDCP Synchronization | Huawei, CBN, China Unicom, China Telecom |
| R3-214030 | Issues on Mobility between MBS Supporting Nodes | LG Electronics |
| R3-214096 | Discussion on Mobility with Service Continuity | CMCC |
| R3-214097 | Discussion on PDCP Synchronization | CMCC |
| R3-214216 | CB: # MBS6_MobilitySupporting - Summary of email discussion | Qualcomm - moderator |
| R3-214239 | Way Forward on Mobility between MBS supporting nodes | Huawei, Qualcomm Incorporated, CMCC, Lenovo, Nokia, Nokia Shanghai Bell, CBN, China Telecom, CATT, LG Electronics, Samsung, China Unicom, BT, vivo |
| R3-214359 | CB: # MBS6_MobilitySupporting - Summary of email discussion | Qualcomm - moderator |
| 22.3.2 | Mobility Between MBS Supporting and non-MBS Supporting Nodes | |
| R3-213240 | (TP for TS 38.300) Mobility with non-MBS supporting NG-RAN nodes | ZTE |
| R3-213463 | (TP for 38.300) Mobility with non-MBS supporting NG-RAN nodes | Nokia, Nokia Shanghai Bell |
| R3-213596 | On open items concerning handover between gNBs supporting NR MBS and gNBs not supporting NR MBS | Ericsson |
| R3-213739 | Mobility between MBS Supporting and non-Supporting nodes | Lenovo, Motorola Mobility |
| R3-213988 | (TP to TS 38.300 BL CR) Mobility between MBS supporting and non-supporting nodes | Huawei, CBN, China Unicom, China Telecom |
| R3-214098 | Discussion on Mobility between non-MBS supporting node and MBS supporting node | CMCC |
| R3-214217 | CB: # MBS7_MobilityNonSupporting - Summary of email discussion | Nokia - moderator |
| R3-214284 | (TP for 38.300) Mobility with non-MBS supporting NG-RAN nodes | Nokia, Nokia Shanghai Bell |
| R3-214295 | LS on Full Configuration in handover to MBS non-supporting gNB | Lenovo, Motorola Mobility |
| R3-214308 | CB: # MBS7_MobilityNonSupporting - Summary of email discussion | Nokia - moderator |
| R3-214416 | (TP for 38.300) Mobility with non-MBS supporting NG-RAN nodes | Nokia, Nokia Shanghai Bell |
| R3-214462 | LS on Full Configuration in handover to MBS non-supporting gNB | Lenovo, Motorola Mobility |
| 22.4 | Others | |
| R3-213464 | (TP for 38.300) Stage 2 for Broadcast Continuity | Nokia, Nokia Shanghai Bell |
| R3-213546 | Remaining Issues on MBS Service Continuity for Broadcast Session | CATT,CBN |
| R3-213790 | Discussion on MBS establishment and mobility in case of common gNB-CU-UP deployment | ZTE |
| R3-213990 | (TP to TS 38.300 BL CR) Broadcast service continuity | Huawei, CBN, China Telecom |
| R3-213991 | Effects of NR MBS related network planning on NG-RAN architecture | CHENGDU TD TECH LTD. |
| R3-214218 | CB: # MBS8_Others - Summary of email discussion | ZTE - moderator |
| R3-214447 | CB: # MBS8_Others - Summary of email discussion | ZTE - moderator |
| 23.1 | General | |
| R3-213165 | CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB | Huawei, Ericsson |
| R3-213166 | CR to 38.462 on the introduction of new interface | Huawei, Ericsson |
| R3-213167 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-213168 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-213176 | Further discussions on logical entities and corresponding definitions | Huawei, Ericsson |
| R3-214225 | CB: # eNBarchEvo1_BLCRs - Summary of email discussion | China Unicom - moderator |
| R3-214487 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-214488 | Further discussions on logical entities and corresponding definitions | Huawei, Ericsson |
| R3-214489 | CR to 38.462 on the introduction of new interface | Huawei, Ericsson |
| R3-214490 | CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB | Huawei, Ericsson |
| 23.2.1 | General Principles, Functions and Procedures | |
| R3-213335 | Further discussions on general aspects for enhanced eNB architecture | Huawei |
| R3-213336 | (TP for BL CR TS 38.401) stage 2 TP for enhanced eNB architecture | Huawei, China Unicom, Orange, Telecom Italia |
| R3-213337 | (TP for BL CR TS 38.460) enhanced eNB architecture | Huawei, China Unicom, Orange, Telecom Italia |
| R3-213338 | (TP for BL CR TS 36.401) stage 2 TP for enhanced eNB architecture | Huawei, China Unicom, Orange, Telecom Italia |
| R3-213483 | (TP for BL CR TS 36.401) stage 2 TP for enhanced eNB architecture | Nokia, Nokia Shanghai Bell |
| R3-213875 | (TP for Enh-eNB Arch Evol BL CR for TS 36.401) CP-UP separation for eNBs | Ericsson |
| R3-213914 | (TP for LTE_NR_arch_evo_enh BL CR for TS 38.401) Discussion on the clarification of E1 interface in NG-RAN and E-UTRAN | Samsung |
| R3-213915 | (TP for LTE_NR_arch_evo_enh BL CR for TS 36.401) Discussion on the features supported by E1AP in E-UTRAN | Samsung |
| R3-213916 | (TP for LTE_NR_arch_evo_enh BL CR for TS 38.460) Clarification of E1 interface | Samsung |
| R3-214226 | CB: # eNBarchEvo2_General - Summary of email discussion | Samsung - moderator |
| 23.2.2 | Signaling Transport | |
| R3-213333 | Further discussions on signalling transport for the new interface | Huawei |
| R3-213334 | (TP for BL CR TS 38.462) Signalling transport to the new interface | Huawei |
| R3-213876 | Transport of UP data for LTE CP/UP split in E-UTRAN | Ericsson |
| R3-213877 | Transport of UP data - Introduction of E-UTRA PDCP in NR UP protocol | Ericsson |
| R3-214227 | CB: # eNBarchEvo3_CPUPTransport - Summary of email discussion | Ericsson - moderator |
| R3-214347 | Transport of UP data - Introduction of E-UTRA PDCP in NR UP protocol | Ericsson |
| R3-214357 | (TP for BL CR TS 38.462) Signalling transport to the new interface | Huawei |
| 23.2.3 | Application Protocol | |
| R3-213339 | Further discussion on stage 3 details | Huawei |
| R3-213340 | (TP for BL CR TS 38.463) Stage 3 update to the new interface | Huawei |
| R3-213878 | E1 changes needed for eNB CP-UP separation | Ericsson |
| R3-213879 | (TP for Enh-eNB Arch Evol BL CR for TS 38.463) E1 changes needed for eNB CP-UP separation | Ericsson |
| R3-214228 | CB: # eNBarchEvo4_E1AP - Summary of email discussion | Huawei - moderator |
| R3-214346 | (TP for BL CR TS 38.463) Stage 3 update to the new interface | Huawei |
| R3-214358 | (TP for BL CR TS 38.463) Stage 3 update to the new interface | Huawei, Ericsson |
| 30.1 | NB-IoT and eMTC support for NTN | |
| R3-213347 | Initial discuss about NB-IoT and eMTC support for NTN | Huawei |
| R3-213597 | Applicability of results from NR NTN to NB-IoT and eMTC NTN | Ericsson |
| 30.3 | Others | |
| R3-213881 | Support of Enhancement of Redundant PDU Sessions | Nokia, Nokia Shanghai Bell |
| R3-213882 | Support of Enhancement of Redundant PDU Sessions | Nokia, Nokia Shanghai Bell |
| R3-213883 | Support of Enhancement of Redundant PDU Sessions | Nokia, Nokia Shanghai Bell |
| R3-213884 | Support of Enhancement of Redundant PDU Sessions | Nokia, Nokia Shanghai Bell |
| R3-213903 | Supporting PDU session pair for redundant transmission | Huawei |
| R3-213904 | Supporting PDU session pair for redundant transmission | Huawei |
| R3-213905 | Supporting PDU session pair for redundant transmission | Huawei |
| R3-213906 | Supporting PDU session pair for redundant transmission | Huawei |
| R3-214102 | Work planning of R17 Sidelink Relay WI (for information) | CMCC, OPPO |
| R3-214229 | CB: # 36_ RedundantPDUSession - Summary of email discussion | Nokia - moderator |
| R3-214243 | Support of Enhancement of Redundant PDU Sessions [Paired_ID] | Nokia, Nokia Shanghai Bell |
| R3-214244 | Support of Enhancement of Redundant PDU Sessions [Paired_ID] | Nokia, Nokia Shanghai Bell |
| R3-214245 | Support of Enhancement of Redundant PDU Sessions [Paired_ID] | Nokia, Nokia Shanghai Bell |
| R3-214336 | Support of Enhancement of Redundant PDU Sessions [Paired_ID] | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, LG Electronics, CATT, Samsung |
| R3-214337 | Support of Enhancement of Redundant PDU Sessions [Paired_ID] | Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, Huawei, CATT, Samsung |
| R3-214338 | Support of Enhancement of Redundant PDU Sessions [Paired_ID] | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, LG Electronics, CATT, Samsung |
| 31.1.1 | Inclusive Language Review | |
| R3-213135 | LS on Inclusive language for ANR | SA5 |
| R3-213775 | Inclusive Language Review Status and Consistency Check | Ericsson (Coordinator) |
| R3-213782 | [DRAFT] Reply LS on Inclusive Language for ANR | Ericsson LM |
| R3-214004 | Inclusive language cleanup for TS25.484 | ZTE |
| R3-214188 | CB: # 27_InclusiveLanguage - Summary of email discussion | Ericsson - moderator |
| R3-214289 | Reply LS on Inclusive Language for ANR | Ericsson LM |
| R3-214293 | Inclusive language cleanup for TS25.484 | ZTE |
| 31.2.1 | Local NG-RAN Node Identifier | |
| R3-213247 | Discussion on I-RNTI partitioning | ZTE |
| R3-213248 | CR for TS 38.423 on I-RNTI partitioning | ZTE |
| R3-213465 | Support of Local NG-RAN node identifier | Nokia, Nokia Shanghai Bell |
| R3-213466 | Support of Local NG-RAN node identifier [Local_Node_ID] | Nokia, Nokia Shanghai Bell |
| R3-213558 | Discussion on Local NG-RAN Node Identifier | Huawei |
| R3-213559 | Local NG-RAN Node Identifier | Huawei |
| R3-213830 | Node Identifier for RRC Inactive | Ericsson |
| R3-213831 | Addition of multiple Local gNB Identifiers per NG-RAN node [RRCInactive] | Ericsson |
| R3-214190 | CB: # 28_LocalNG-RANnode_Identifier - Summary of email discussion | Ericsson - moderator |
| R3-214263 | Addition of multiple Local gNB Identifiers per NG-RAN node [RRCInactive] | Ericsson |
| R3-214456 | CB: # 28_LocalNG-RANnode_Identifier - Summary of email discussion | Ericsson - moderator |
| 31.2.2 | RRC Reject Template for the gNB-DU | |
| R3-213419 | RRC Reject Template for the gNB-DU | Ericsson |
| R3-213474 | Discussion on RRC Reject Template | Nokia, Nokia Shanghai Bell |
| R3-213475 | RRC Reject Template [REJECT_TEM] | Nokia, Nokia Shanghai Bell |
| R3-214082 | Further discussions on RRC reject template for the gNB-DU | Huawei |
| R3-214088 | Consideration on Template RRC Reject for gNB-DU | ZTE |
| R3-214191 | CB: # 29_RRCRejectDU - Summary of email discussion | Huawei - moderator |
| 31.2.3 | PRACH Coordination Between LTE and NR | |
| R3-213560 | PRACH Coordination Between LTE and NR | Huawei |
| R3-213781 | On coordination of PRAH resources among LTE and NR cells with no direct interface | Ericsson |
| R3-213810 | Consideration on the PRACH Coordination between LTE and NR | ZTE |
| R3-213897 | Resource Coordination between LTE and NR in Overlapping Spectrum | China Telecom, CATT,ZTE |
| R3-213898 | draft LS on the support of non-collocated co-channel deployment of NR and LTE | China Telecom Corporation Ltd. |
| R3-214192 | CB: # 30_PRACHCoordination - Summary of email discussion | China Telecom - moderator |
| R3-214362 | draft LS on the support of non-collocated co-channel deployment of NR and LTE | China Telecom Corporation Ltd. |
| 31.2.4 | Others | |
| R3-213253 | Data forwarding in case of a HO to wrong cell | Nokia, Nokia Shanghai Bell |
| R3-213315 | Discussion on UL PDCP duplication | ZTE |
| R3-213401 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-213402 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-213403 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-213467 | Dual Connectiviy Support with Slicing | Nokia, Nokia Shanghai Bell |
| R3-213478 | Discussion on NSA-SA Cell Operation | Nokia, Nokia Shanghai Bell |
| R3-213561 | Correction on release-with-redirect in 2-step RRC resume procedure | Huawei, China Unicom, CMCC |
| R3-213562 | Correction on release-with-redirect in 2-step RRC resume procedure | Huawei, China Unicom, CMCC |
| R3-213625 | Assistance information for UL duplication | Huawei, China Unicom, China Telecom, CATT |
| R3-213626 | Assistance information for UL duplication | Huawei, China Unicom, China Telecom, CATT |
| R3-213857 | Support for TA-based measurement reporting in NR E-CID positioning | Ericsson, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, CATT |
| R3-213858 | Addition of gNB Rx-Tx measurement reporting in NR E-CID [TAtype2] | Ericsson, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, CATT |
| R3-213859 | Discussion on CSI-RS configuration exchange | Ericsson, China Telecom |
| R3-213860 | Signalling of Neighbour cell CSI-RS configuration information over Xn [CSIRSXn] | Ericsson, China Telecom |
| R3-213861 | Signalling of Neighbour cell CSI-RS configuration information over X2 [CSIRSX2] | Ericsson, China Telecom |
| R3-213917 | Assistance information for UL duplication | Huawei, China Unicom, China Telecom, CATT |
| R3-213954 | Discussion on UL PDCP Duplication | CATT |
| R3-213955 | CR to 38.425 for handling of UL PDCP Duplication status information | CATT |
| R3-214014 | Clarification on NPN Mobility Information for XNAP | ZTE Corporation |
| R3-214015 | Clarification on NPN Mobility Information for NGAP | ZTE Corporation |
| R3-214193 | CB: # 31_ULPDCPDuplication - Summary of email discussion | CATT - moderator |
| R3-214251 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-214273 | CB: # 117_CellOperation - Summary of email discussion | Nokia - moderator |
| R3-214274 | CB: # 118_CSIRSConifg - Summary of email discussion | Ericsson - moderator |
| R3-214275 | CB: # 119_RxTxMeasureReport - Summary of email discussion | Ericsson - moderator |
| R3-214276 | CB: # 120_NPNMobilty - Summary of email discussion | ZTE - moderator |
| R3-214436 | Clarification on NPN Mobility Information for XNAP | ZTE Corporation, Nokia, Nokia Shanghai Bell |
| R3-214437 | Clarification on NPN Mobility Information for NGAP | ZTE Corporation, Nokia, Nokia Shanghai Bell |